The elephant in the room is IRC. Which continues to work fine and hosts huge FOSS communities. Self hosting it is even better as you can use a more modern version like ergo.chat than the large networks sadly utilize.
But IRC doesn’t really support E2EE in 1:1 chats right? Because that’s something very important for me. I don’t want to use an app only for public channels I ideally would like to use it for everything. Including messaging the people I know.
There are some ways to make it work with OTR, but realistically speaking no.
Personally I get around that by using XMPP and connecting to IRC via the excellent Biboumi gateway. Thus I get the best of both, as XMPP is working really well for e2ee 1:1 chats.
IRCv3 has a lot of features & is good, but if you need encrypted chat and/or want to support decentralization XMPP MUCs can fit the bill similar being just a bit less lightweight.
I use IRC in Matrix, and have used IRC since the 90s, but IRC lacks many modern features, even simple things like configurable push notifications and universal encryption, perhaps ergo is better? But then again, the reason I chose Lemmy was distribution, so…
Heh, push notifications and universal encryption are about the opposite of simple and fail to work on Matrix most of the time. Most of the actually simple and useful features for a public chat are supported by Ergo though.
What issues have you had? Using Element worked out of the box for me on both. Even spun up my own server with a docker compose and it worked fine there, too.
Large public rooms have constant issues with encryption, and since you can’t turn it off once enabled (yeah 🤦♂️) most public rooms are not e2ee. Besides the fact that e2ee doesn’t really make sense in public rooms as anyone can join.
Push notifications in Matrix clients only work with the help of Google’s or Apple’s centralized infrastructure. This is of course only partially the fault of Matrix, but XMPP for example can do it without pretty well.
Yes, FluffyChat wants ntfy but Element has their own background service in the F-Droid package. Still fits the bill of not using Google infrastructure.
These support UnifiedPush, not just ntfy. UnifiedPush is an open protocol whereas ntfy is an implementation of UnifiedPush. I use my Prosody server to deliver my UnifiiedPush notifications.
The elephant in the room is IRC. Which continues to work fine and hosts huge FOSS communities. Self hosting it is even better as you can use a more modern version like ergo.chat than the large networks sadly utilize.
You made me look again at IRC V3, seems like they support threads and emoji reactions. I might give it a try
But IRC doesn’t really support E2EE in 1:1 chats right? Because that’s something very important for me. I don’t want to use an app only for public channels I ideally would like to use it for everything. Including messaging the people I know.
There are some ways to make it work with OTR, but realistically speaking no.
Personally I get around that by using XMPP and connecting to IRC via the excellent Biboumi gateway. Thus I get the best of both, as XMPP is working really well for e2ee 1:1 chats.
IRCv3 has a lot of features & is good, but if you need encrypted chat and/or want to support decentralization XMPP MUCs can fit the bill similar being just a bit less lightweight.
Does IRC have a pluralkit equivalent?
I use IRC in Matrix, and have used IRC since the 90s, but IRC lacks many modern features, even simple things like configurable push notifications and universal encryption, perhaps ergo is better? But then again, the reason I chose Lemmy was distribution, so…
Heh, push notifications and universal encryption are about the opposite of simple and fail to work on Matrix most of the time. Most of the actually simple and useful features for a public chat are supported by Ergo though.
What issues have you had? Using Element worked out of the box for me on both. Even spun up my own server with a docker compose and it worked fine there, too.
Large public rooms have constant issues with encryption, and since you can’t turn it off once enabled (yeah 🤦♂️) most public rooms are not e2ee. Besides the fact that e2ee doesn’t really make sense in public rooms as anyone can join.
Push notifications in Matrix clients only work with the help of Google’s or Apple’s centralized infrastructure. This is of course only partially the fault of Matrix, but XMPP for example can do it without pretty well.
push notifications also work degoogled on element and fluffychat, what do you mean?
Source? I am pretty sure you need workarounds like Unified Push to a 3rd party app then.
Yes, FluffyChat wants ntfy but Element has their own background service in the F-Droid package. Still fits the bill of not using Google infrastructure.
These support UnifiedPush, not just ntfy. UnifiedPush is an open protocol whereas ntfy is an implementation of UnifiedPush. I use my Prosody server to deliver my UnifiiedPush notifications.