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.
hillarious way to advertise, chum.
Haven't they heard about IRC (RFCs 1459, 2810–2813)?
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.
MSN Messenger's protocol was submitted to the ECMA in 1999, but MS made changes to their implementation almost immediately that were never documented.
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)
centre is basically a copy of hipchat...
Has anyone tried Let's Talk, Shout, Echoplex, and/or Kaiwa in practice and have some experiences to share? Stability, searchability, general functionality?
This is, ofc, my $0.02. Stuck in the old way of doing things, I guess.
Still pretty cool, particularly the deploy on DO.
There are a few different solutions for this out there, especially clients that run some custom protocol between the GUI and the bouncer, like Quassel and Smuxi - but I've tried both, and each both (a) has poor mobile support and (b) once you get used to it, turns out to just suck in general. (These opinions are a few years out of date, though.)
Thankfully I don't actually care much about mobile support: I don't use IRC for time-sensitive discussions, and for recreational purposes, trying to participate in a real-time conversation where everyone can type several times faster than you is, IMO, a pain; I'm faster at typing on iOS than I used to be, but it's still just not comparable to a real keyboard. Better to save the chatting for when I have one. But I find ssh+screen an unacceptable solution: partly because of issues with notifications (i.e. out of the box, there are none) and copy+paste, though both can be fixed in theory, but mainly because of the latency. When the letters I type don't appear for 100ms or more, it really trips me up and I make a lot more typos. I could find a server with less latency at home, but that wouldn't help when traveling, especially on an unreliable connection - even though there is no fundamental reason chat should be latency sensitive in the slightest. Tried mosh (ssh + prediction) as a compromise for a while, and it works better, but it has some issues and doesn't fully hide the latency.
These days I'm using Glowing Bear, the web-based remote for weechat (that uses yet another custom protocol). Latency's gone, and like other web-based clients it has the neat feature of embedding YouTube videos and images, so I'm finally pretty satisfied with my IRC setup. (And I can be paranoid about security and run it on localhost rather than using their website directly.) But there are disadvantages: Glowing Bear is somewhat feature poor, it (again like other web-based clients) is relatively slow to render, and there is no native iOS weechat remote. (Guess I could still use weechat as a regular bouncer, or perhaps try Glowing Bear from mobile Safari...)
Like for you IRC isn't anything beyond recreational for me, so quirks in the workflow are just fine to work around. If it was my primary method of communication I'd be looking into improving it I suspect.
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.
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.
I just wish these were easier ''FOR ME'' to install on FreeBSD.
It's not like it's revolutionary. They put two and two together in the only reasonable manner for a single-page application.
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).
The call is still open on end-to-end encryption over XMPP when multiple devices (or more than two parties) are involved.
Is there any chat system out there with end-to-end crypto and reasonable support for multiple devices?
Besides, it is not available for non-Apple devices.
TextSecure/Signal has a robust crypto system, and they are working on multi-device support.
How about hosting E2E js lib somewhere like on Github and include them there?
Or you can always map to local js files.
- 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)
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).
I'm ONLY using Hangouts because they don't allow group messaging in any other client. I'd like to see that change!
Is there a reason why you chose Prosody over MongooseIM or ejabberd?
I love to receive feedback (of any kind), as it's the only way we know what we're doing right and wrong!
The beta's limitations are:
* rather broken invitation handling user interface
* cumbersome MUC joining user interface
* impossible to downgrade to non-beta builds
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.
I find that in practice I can _sometimes_ communicate with _some_ users from _some_ clients, but it seems like it's flaky and there's not a clear pattern to it. Do you have any deeper insight?