Browse Source

Cleaning up format of broadcast real-time messages, removing
redis-backed "mentions" timeline as redundant (given notifications)

Eugen Rochko 7 years ago
parent
commit
e26dcda6e7
2 changed files with 2 additions and 1 deletions
  1. 0 1
      Using-the-API/API.md
  2. 2 0
      Using-the-API/Push-notifications.md

+ 0 - 1
Using-the-API/API.md

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

+ 2 - 0
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"