bida/Mastodon-documentation
6
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Cleaning up format of broadcast real-time messages, removing

Browse source 
redis-backed "mentions" timeline as redundant (given notifications)
This commit is contained in:
Eugen Rochko 2017-02-02 00:03:31 +01:00
parent a4b55cc670
commit e26dcda6e7
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
Using-the-API/API.md
View file

@ -65,7 +65,6 @@ Returns a media object with an ID that can be attached when creating a status (s
### Retrieving a timeline ### Retrieving a timeline
**GET /api/v1/timelines/home** **GET /api/v1/timelines/home**
**GET /api/v1/timelines/mentions**
**GET /api/v1/timelines/public** **GET /api/v1/timelines/public**
**GET /api/v1/timelines/tag/:hashtag** **GET /api/v1/timelines/tag/:hashtag**

2
Using-the-API/Push-notifications.md
View file

@ -1,6 +1,8 @@
Push notifications 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: 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" * 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"