diff options
author | Eugen Rochko <eugen@zeonfederated.com> | 2017-02-02 00:03:31 +0100 |
---|---|---|
committer | Eugen Rochko <eugen@zeonfederated.com> | 2017-02-02 00:03:31 +0100 |
commit | d9ca46b464dc5a5eb0ad308809c15a79dcd17ada (patch) | |
tree | 481d65b29b53d84314f7783c1eb0f4b122e7a7ef /docs/Using-the-API/Push-notifications.md | |
parent | 1da0ce5c7cf6a5b90e28a810c8b3ef4003239383 (diff) |
Cleaning up format of broadcast real-time messages, removing
redis-backed "mentions" timeline as redundant (given notifications)
Diffstat (limited to 'docs/Using-the-API/Push-notifications.md')
-rw-r--r-- | docs/Using-the-API/Push-notifications.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/Using-the-API/Push-notifications.md b/docs/Using-the-API/Push-notifications.md index 746bf65ef..fd50a75bd 100644 --- a/docs/Using-the-API/Push-notifications.md +++ b/docs/Using-the-API/Push-notifications.md @@ -1,6 +1,8 @@ Push notifications ================== +**Note: This push notification design turned out to not be fully operational on the side of Firebase. A different approach is in consideration** + Mastodon can communicate with the Firebase Cloud Messaging API to send push notifications to apps on users' devices. For this to work, these conditions must be met: * Responsibility of an instance owner: `FCM_API_KEY` set on the instance. This can be obtained on the Firebase dashboard, in project settings, under Cloud Messaging, as "server key" |