31–40 of 142 posts
In my opinion, it doesn't matter if it looks like Slack. What matters is that I can deploy it on an existing infrastructure and still have control over the service instead of handing over control to a third-party.
This is, ofc, my $0.02. Stuck in the old way of doing things, I guess.
Still pretty cool, particularly the deploy on DO.
In my opinion, it doesn't matter if it looks like Slack. What matters is that I can deploy it on an existing infrastructure and still have control over the service instead of handing over control to a third-party.
I for one welcome slack competitors, self-hostable, open sources ones especially.
Earlier quoted context omitted.
Thank you. We chose Prosody because it supports the XEP we needed and it was originally used by Otalk from which we forked.
Relatedly, why are you recommending only Pidgin, and not Gajim? Gajim covers a lot more XEPs than Pidgin (e.g. editing sent message).
If you disabled or drastically resized the avatars and put the usernames not in a separate line, the window could hold a lot more content for single-line conversations like that.
The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?
The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?