From e26dcda6e75181d06fe8987a6b09699e8bc86ddc Mon Sep 17 00:00:00 2001
From: Eugen Rochko <eugen@zeonfederated.com>
Date: Thu, 2 Feb 2017 00:03:31 +0100
Subject: [PATCH] Cleaning up format of broadcast real-time messages, removing
 redis-backed "mentions" timeline as redundant (given notifications)

---
 Using-the-API/API.md                | 1 -
 Using-the-API/Push-notifications.md | 2 ++
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/Using-the-API/API.md b/Using-the-API/API.md
index fecc6c59..51b46592 100644
--- a/Using-the-API/API.md
+++ b/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**
 
diff --git a/Using-the-API/Push-notifications.md b/Using-the-API/Push-notifications.md
index 746bf65e..fd50a75b 100644
--- a/Using-the-API/Push-notifications.md
+++ b/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"