9ec5d6e3b0
Fixes #793. This is an implementation for push notifications based on UnifiedPush for Tusky. No push gateway (other than UP itself) is needed, since UnifiedPush is simple enough such that it can act as a catch-all endpoint for WebPush messages. When a UnifiedPush distributor is present on-device, we will by default register Tusky as a receiver; if no UnifiedPush distributor is available, then pull notifications are used as a fallback mechanism. Because WebPush messages are encrypted, and Mastodon does not send the keys and IV needed for decryption in the request body, for now the push handler simply acts as a trigger for the pre-existing NotificationWorker which is also used for pull notifications. Nevertheless, I have implemented proper key generation and storage, just in case we would like to implement full decryption support in the future when Mastodon upgrades to the latest WebPush encryption scheme that includes all information in the request body. For users with existing accounts, push notifications will not be enabled until all of the accounts have been re-logged in to grant the new push OAuth scope. A small prompt will be shown (until dismissed) as a Snackbar to explain to the user about this, and an option is added in Account Preferences to facilitate re-login without deleting local drafts and cache. |
||
|---|---|---|
| .. | ||
| 10.json | ||
| 11.json | ||
| 12.json | ||
| 13.json | ||
| 14.json | ||
| 15.json | ||
| 16.json | ||
| 17.json | ||
| 18.json | ||
| 19.json | ||
| 20.json | ||
| 21.json | ||
| 22.json | ||
| 23.json | ||
| 24.json | ||
| 25.json | ||
| 26.json | ||
| 27.json | ||
| 28.json | ||
| 29.json | ||
| 30.json | ||
| 31.json | ||
| 32.json | ||
| 33.json | ||
| 34.json | ||
| 35.json | ||
| 36.json | ||