Gregory's ServerThe one-click Push Notification setup will allow you to self register with the gateway and get an API key from the admin dashboard!
No emailing to request an API key or editing your .env required, available soon!
 13 comments
@grishka Yeah this is temporary using expo-notifications (https://docs.expo.dev/push-notifications/overview/) The long term goal is to match Mastodon in terms of the push notification API and use a generic app proxy  dansup, Mastodon does also require proxies, every app developer provides one for their own app. It can only send web push natively. I'm contemplating push notifications for Smithereen (I'll have to have them with the API) but I don't want to require app developers to host a proxy, so I'm thinking about giving them the ability to include their FCM/APNS tokens in the app metadata. But they'll still have the option to use a proxy, of course.  feld, what do you mean by "allow"? They do both tell you to "keep them secure", but I can't imagine them revoking the keys that are useless without device tokens anyway. @grishka @dansup there was a misunderstanding on my end; I agree with your description, that's how I understand it. We made a push proxy called Charisma for apps we were working on along side Pleroma so this is familiar.
if there was the ability to *not* have a push proxy run by the app developers it would be great. I strongly support your proposal.  @dansup So are you using a centralized push notification service that you maintain for this? Or how does this work from a technical perspective? |
After reading through the docs for both FCM and APNS, I feel like the intermediary server isn't actually necessary, you can have each individual instance send its own push notifications directly to Google/Apple. If you instruct app developers to create separate API keys just for push notifications, no harm could be done with them because you'd also need a device token to actually send something.