this post was submitted on 02 Mar 2024
1324 points (96.2% liked)
Open Source
31243 readers
240 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.