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.

[–] poVoq@slrpnk.net 1 points 8 months ago (1 children)

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.

[–] Cupcake1972@mander.xyz 1 points 8 months ago (1 children)

push notifications also work degoogled on element and fluffychat, what do you mean?

[–] poVoq@slrpnk.net 1 points 8 months ago (1 children)

Source? I am pretty sure you need workarounds like Unified Push to a 3rd party app then.

[–] Cupcake1972@mander.xyz 1 points 8 months ago (1 children)

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.

[–] toastal@lemmy.ml 3 points 8 months ago

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.