Am looking into that as well. What endpoint are you registering device tokens against? At least on iOS you cannot register decices against the official bsky backend because of differing signing keys (app, backend).
1 1Could you generate a FCM Registration Token and register that instead? I believe it then connects to APNs through FCM firebase.google.com/docs/cloud-m...
There's a APNs authentication key but maybe their backend accepts any push token?
1 2Even if you connect your FCM to your APNS account (which is possible), how are you getting the notifications from Bluesky to YOUR FCM instance?
2 2As far as I understand the library it only handles the client-side of push notifications. The issue I have is that i don’t see a way to enable bsky to push notifications to firebase/apns that then get delivered to 3rd party apps. For that to work bsky would need the 3rd party‘s push certificate.
1Yeah and then bsky sends the push notifications using that token and a shared certificate (shared btw app and backend). APNS checks if the app it sends the notifications to has a matching certificate. That’s the problem I see. 3rd party apps have their own push credentials.
1 2how does the push notification endpoint work? is it a lexicon or something unspecced
1 1for example did:web:api.bsky.app, which you can see here
api.bsky.app/.well-known/did.json
https://api.bsky.app/.well-known/did.json
api.bsky.app
ah, so you run your own server, and it receives a webhook-shaped thing and then can decide how to forward to devices. makes sense, i think
1 3Samuel
@samuel.fm
My plan is to send it to a nextjs edge function and then onto firebase/apn. although the js push notification ecosystem seems terrible so I might have to choose between self hosted gorush (tricky) or something like OneSignal (vendor lock-in :/ )
1 1