Thread

https://unifiedpush.org We have not yet started implementing unified push. Unified push requires users to download a separate app to receive push notifications. Some users may adopt unified push while others will continue using the existing solutions. We need to find a way to support both approaches concurrently.

Users that focus on #privacy and want to benefit from #unifiedpush currently need to download an app (#foss ). That's right. Similar case like for most #vpn provider client software. The #unifiedpush app they have chosen is not only to gain #sovereignty and #privacy regarding this particular app which provides notifications (e.g. #keychat hopefully in near future). It is the foundation for any other app relying on #pushnotifications on their system that supports #unifiedpush . Some users have their #unifiedpush app of choice already installed and benefit from the #networkeffect and #synergy . Others have to take their first steps👣to gain more #sovereignty and #privacy. It's the natural🌱way to gain more traction on this topics. What do you referencing by "existing solutions" apart from Firebase Cloud Messaging #fcm and Apple Push Notification Service #apn ? ⚠️Which both are not preserving users #metadata #GOS #grapheneos users would love❤️an implementation🔧of the #unifiedpush feature too🔒 It should also be mentioned that by using #unifiedpush users have got the choice to #selfhost their own push notifications #server and do not have to rely on any other third party service. #docker images support this approach for users already. We all need more #privacy and #freedom🌐⛓️

We completely agree. In Keychat, the message relay, media relay, and Cashu mint are all user-configurable by design. We’re aware that notifications are currently the weakest link since users can’t manage them independently yet, and we will continue moving in that direction.