Mozilla officially refuse to support UnifiedPush, which was incredibly exciting and something I was eager to see land.
You must log in or # to comment.
To make it easier:
Polly [:polly] Comment 21 • 4 hours ago As discussed on the attached patch, it doesn't sound like unified push is a direction we want to go in at the moment. So i'm going to close the bug, but do appreciate the interesting exploration and discussion it has generated. Thank you to everyone who contributed thoughts, time and code to this issue! Status: ASSIGNED → RESOLVED Closed: 4 hours ago Resolution: --- → WONTFIX
The comment that was being referenced (I think):
pollymce requested changes to this revision.Fri, Jun 27, 11:17 AM pollymce added a subscriber: pollymce. Comment Actions hello - thank you for looking into this and submitting this patch stack! I have asked around a few people internally but unfortunately, there doesn't seem to be a lot of support for the idea of moving to Unified Push. So I think it would be best to abandon the stack rather than spend more time working on this implementation. Sorry to have to say that and sorry it's taken so long to get back to you with this message! We appreciate your time and effort here and hope that you will still consider contributing to firefox in the future.EDIT: Copy pasted the text for accessibility
But even this is down to a lack of understanding. No one is talking about switching Fenix to UnifiedPush by default, rather it’s about providing the option.
This is just a shame :/
private notifications is not a direction Mozilla wants to be going. better keep relying on the services of a datamining based adtech company for it.
