Haven't they heard about IRC (RFCs 1459, 2810–2813)?
</blatant self-promotion>
There seems to be this general assumption at the moment that a) XMPP is the only open chat protocol about and b) its dead, so everyone decides that the only logical course of action is to write and use custom proprietary protocol. This, of course, massively sucks from a UX perspective where I end up having 100s of identities and apps and logins that I use (semi-)regularly to not just chat with people, but also comment on articles, discuss things on mailing lists etc.
Edit: whoops, I had commented once before, it was just so long ago that I forgot about it!
That and the use of hashtags to group things together on Twitter, etc.
I guess it's just a "thing" now.
I deeply appreciate the history and communities available on IRC, but as a protocol, good riddance to it.
[0] http://en.wikipedia.org/wiki/IRCd#/media/File:IRCd_software_...
MSN Messenger's protocol was submitted to the ECMA in 1999, but MS made changes to their implementation almost immediately that were never documented.
And its nice to be able to choose which apps you want to use on all the different platforms; and choose differently than everyone else. The app that works for me isn't necessarily the app that works for others, but I still want to be able to talk to them using the app I want.
This is, ofc, my $0.02. Stuck in the old way of doing things, I guess.
Still pretty cool, particularly the deploy on DO.
Quick google found https://github.com/paddykontschak/irssi-notifier/blob/master...
I don't bother with it though. If I'm away from a computer, I don't need to see it.
Quite the contrary: Project and knowledge management or so important that you should not have just one (and additionally closed-source) application for that.
It's good to have competitors who focus on different workflows (Evernote was not built to be collaborative, Trello does not offer other display modes such as cards and a basic calendar).
I would not complain if they created another CRM as simple as Highrise or an open source helpdesk that could replace Zendesk (I really like helpful.io for this, btw).
More seriously, what's the problem here? Maybe they actually take security seriously (compared to Evernote), and maybe syncing on Polynote isn't fundamentally broken! (a boy can dream)
Are there open source projects that use XMPP for their public channels?
I'm a little dismayed by how many Slack accounts I'm acquiring.
Sure, but we have TLS for that. E2E is still needed to cover everything else (e.g., I trust the server now, but I don't want to have plain-text logs on it in case the feds seize it).
How about hosting E2E js lib somewhere like on Github and include them there?
Or you can always map to local js files.
https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypt...
Is there a reason why you chose Prosody over MongooseIM or ejabberd?
1: https://github.com/otalk/otalk-im-client/compare/master...di...
I love to receive feedback (of any kind), as it's the only way we know what we're doing right and wrong!
I just wish these were easier ''FOR ME'' to install on FreeBSD.
[0] https://github.com/digicoop/kaiwa-server/blob/master/README....
- Will this stay connected to my account and the history will be there if I close the tab / browser / computer in the meantime?
- Is it possible to replace certain strings with images? This is not at all an important feature but just something I got used over the years. (Example: :string: replaced with image.png and displayed inline. That's possible with Adium but I'd really like to replace Adium)
Thanks!
Using Message Carbons (XEP-0280) all of your active conversations will be synced to your Kaiwa client.
I understood the question as "will I be able to receive messages while the tab isn't open" (offline messages) and "will I be able to read my history on a different device later on" (MAM). Carbons serve a different purpose and sync connected clients (i.e. you chat on your desktop, but your phone receives the same messages as a carbon copy to stay in sync).
Has anyone tried Let's Talk, Shout, Echoplex, and/or Kaiwa in practice and have some experiences to share? Stability, searchability, general functionality?
It's not like it's revolutionary. They put two and two together in the only reasonable manner for a single-page application.
I'm ONLY using Hangouts because they don't allow group messaging in any other client. I'd like to see that change!
If I remember correctly, "Kaiwa", was the codename for the first Macromedia's Flashcom Server (before Adobe's acquisition).
Flashcom Server at that time made it possible to run 2+ ways multi-threaded communication (audio/video) via the Flash Player (2003-ish).
I think that should say "servers" plural.
need to try it out to see how extensible it is.
lolnope