Did you know that one of the ways Android and IOS reduce energy consumption is by using a unified system-level notification provider?
UnifiedPush is FOSS implementation of the same idea that could help projects such as #pinephone and #linuxphones in general by providing both a framework to reduce battery consumption and a more unified interface to code notifications on.
If you follow FOSS, would you please boost?
@poorpocketsmcnewhold I think one of the issues is that the website itself is not exceptionally clear on if and how a linux-connector is available.
As for android, it's a of a "we need to popularize this and make PRs to apps" type thing.
IE: tusky has an early PR for UnifiedPush that was opened in the lastbfew days
Don't app-devs need to explicitly build support of this into their apps and server components?
If I install this as a user, apps won't magically start using it, right?
This isn't some microG stuff that mocks google services and uses UP in the background, if I'm not mistaken
@loveisgrief Yup. Although it's quite simple to add the connector library client-side, unfortunately the site doesn't have a lot of info for server side implementations
@Mek101 like feel often info is missing.. Too much implicit?!
* What is it. It is showing the users little messages? "Notifier" could mean anything. Is it like zeromq or what..
* Is it really only for phones? Thinking not?
* Is it needed? Like probably there isn't a standard good enough out there yet? Like this question is a PITA, if this thing is neatly implemented and older ones aren't easily grasped, it doesn't require elaborate analysis..
1 An open source reimplementation of a servuce present in Android and IOS: keeping apps open and having them continuously pool or keep open connections to check for remote notifications is energetically expensive. UnifiedPush provides a service and protocol to delegate the duty to a single service.
2 No, it's a protocol and "framework", currently with android implementations
3 Is battery life needed? Also, I don't know of any open substitutes
@jasper Also, it can help in implement new applications, since the developer doesn't have to work on the entire notification stack
@Mek101 Also feel a bit stupid about the C example? It's all receiving, why all the implicitness... "Do this, oh you can receive now." Instead of "this is how you set up", "this is how you receive", which emphasis. (`newMessage` also makes me think "sending" sooner too to be honest..)
Another: there is no sending?
Tbh a bit of a communication gripe. Sorry to reply-guy a bit :/
@Mek101 oh yeah, they also have the mythical "golden socket", or something, which is the only socket which is guaranteed to live. I don't remember how they use it, but yeah. An interesting thing to consider when it comes to running stuff in backgorund.
@Mek101 thanks, I would be very interested in using this. Is it somehow possible to use this as a drop in replacement for google's PN? Will it someday or do you envision a different future? Thanks for the work btw!!
@Santral Unfortunately I'm not one of the developers😅.
As for drop-in replacement, unified push uses a different protocol, so apps need to use a library
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!