Whilst this is theoretically a nice idea for security/privacy, wouldn’t there be throughput/latency concerns over mobile networks if you aren’t just connecting to one server and getting all your notifications in one go? One of the biggest slow downs on mobile data is the initial handshake, so repeating that for each of your apps doesn’t seem worth the trade off to me.
This is the goal, in the same way Google does for FCM: the Play Services maintain a connection with their servers to get the notifications and then send them to the different apps. Here's it's the same with a server you control and know it won't read whatever is in that notification, without draining the battery because there's only the Unified Push app maintaining the connection.
Does it? If you're using an iPhone are you really expecting to be able to use a third party project like this for notificatioms with how locked down IOS is and Apple's limitations on what is allowed to be installed on your device?
Readit News
Aren't notification contents E2E? The website is rather light on details.
Conversations (XMPP Client) is now a UnifiedPush distributor - https://news.ycombinator.com/item?id=34381598 - Jan 2023 (30 comments)
UnifiedPush: A decentralized, open-source push notification protocol - https://news.ycombinator.com/item?id=34094497 - Dec 2022 (146 comments)
[1] https://unifiedpush.org/users/faq/#will-unifiedpush-ever-wor...
you know, just how the Internet Protocol was originally intended.
Deleted Comment