Unified push is great news in general for AOSP based ROMs phones for battery life, it’s an open notification standard and system. There are several providers or distributors. If you’re already using nextCloud with the unified push support on the server (murena has enabled this already because they want apps to consume less energy because of having to run in the background if not wanting to use the proprietary google services notifications) then you can use the unified push app already available on f-droid. If using conversations (xmpp client) it already supports working as an unified push provider and perhaps other xmmp clients already added such support and conversations is also available on f-droid. Or you can use the ntfy provided app also available on f-droid. There’s an apps list available to find out if particular apps already support unified push, and as you can see fennec is one of them. BTW, if one doesn’t want or need push notifications on fennec this can be disabled on its notifications settings, When installing an unified push notification provider, the apps supporting it will attempt to subscribe with a particular topic name on the provider, and usually the providers come with default settings to automatically accept subscriptions, and one can just check if the subscription is there already or not, one might need to stop and re-open the app for it to attempt to subscribe. Make sure the provider is running in the background without restrictions, I can tell conversations and ntfy are pretty low battery consumers so no worries about no restrictions on battery consumption.
Does that help? Otherwise I’m kind of lost with the questiosn.















I believe they are claiming that with the new discoveries it’s pointless to keep trying. Whether that’s shared with other devs or not probably won’t affect their decision:
I’m not that familiar with them, but sounds like there’s no way to keep a sane balance between usability and privacy, and clearly upstream doesn’t help a bit, it’s like following the Borg advice “resistance is futile”. Battling the privacy fight is not an easy fight I guess. The only hope for those who are non experts as the arkenfox guys is that phoenix keeps up the good work. Overall I pretty much prefer arkenfox over phoenix, but fortunately Librewolf is neither arkenfox nor phoenix, even though they are discussing if they are better based of phoenix the are different projects making different decisions…
I wish frozen fennec didn’t die on the attempt, :( The current option is ironfox on LOS/AOSP based/…, and I don’t agree with several of their decisions. The amount of filter lists is so stubbornly huge, that there’s no time to deselect and/or remove them on low end phones for example, and the whole thing just slow things down. And I know it’s picky but I really like decisions like taking bad things off from build time if possible, even if they are opt-in… Any ways, to me it’s sad to see them closing the project, but I’m also hopeful some others as expert as they were on several of the topics they dealt with will fill up some of the the hole when they stop…