| ... | ... | @@ -20,13 +20,11 @@ Outputs: |
|
|
|
|
|
|
|
## Rationale
|
|
|
|
|
|
|
|
**UnifiedPush** frees people from dependence on Big Tech's services for their push notifications, giving a choice of push service provider. Adoption in the freedom-software mobile ecosystem is constrained by the common chicken-and-egg problem: app developers wait for support by their OS (*) and service provider; OS and service providers wait for apps. Any progress to break the circle is helpful.
|
|
|
|
|
|
|
|
> (*) A "power user" on a freedom software OS need not wait for UnifiedPush provision, as they can install a UnifiedPush distributor, grant it sufficient permissions, and connect it to a server of their choosing. However this does not change the equation much for app developers targeting ordinary people.
|
|
|
|
**UnifiedPush** frees people from dependence on Big Tech's services for their push notifications, giving a choice of push service provider. Adoption in the freedom-software mobile ecosystem is constrained by the common chicken-and-egg problem: app developers wait for support by their OS and service provider (even though power users don't need it [^1]); OS and service providers wait for apps. Any progress to break the circle is helpful.
|
|
|
|
|
|
|
|
**Email** is one of the more important and more difficult apps to target. The IMAP-IDLE technique is usually used. Only a few email servers and clients implement the newer JMAP which supports WebPush and so also UnifiedPush. Adding WebPush or UnifiedPush support to any IMAP email client is therefore high effort (implementing JMAP) and low reward (few servers support it) for app developers, and similarly for server developers.
|
|
|
|
|
|
|
|
If IMAP servers would be able to support WebPush, and so also UnifiedPush, then it would be easier to add that support into the existing IMAP email clients, and it would be easier for IMAP servers to provide that support.
|
|
|
|
If **IMAP** servers would be able to support WebPush, and so also UnifiedPush, then it would be easier to add that support into the existing IMAP email clients, and it would be easier for IMAP servers to provide that support.
|
|
|
|
|
|
|
|
|
|
|
|
## Risks
|
| ... | ... | @@ -48,3 +46,6 @@ Even a modest increase in server support might be expected to enable a more than |
|
|
|
- [lttrs-android](https://codeberg.org/iNPUTmice/lttrs-android) supports U-P via JMAP WebPush
|
|
|
|
- [DeltaChat](https://delta.chat/) -- [source](https://github.com/deltachat) -- [other clients](https://support.delta.chat/t/list-of-all-know-client-projects/3059)
|
|
|
|
- [K9-mail](https://k9mail.app/) -- [source](https://github.com/k9mail) -- [closed](https://github.com/thunderbird/thunderbird-android/issues/5123) [issues](https://github.com/thunderbird/thunderbird-android/issues/5165) -- [JMAP request](https://github.com/thunderbird/thunderbird-android/issues/3272) -- [wishlist](https://connect.mozilla.org/t5/ideas/idb-p/ideas/label-name/thunderbird%20android) (this is not on it)
|
|
|
|
|
|
|
|
---
|
|
|
|
[^1]: A "power user" on a freedom software OS need not wait for UnifiedPush provision, as they can install a UnifiedPush distributor, grant it sufficient permissions, and connect it to a server of their choosing. However this does not change the equation much for app developers targeting ordinary people. |
