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 1
Could 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 2Samuel
@samuel.fm
Ah I see. @ansh.bsky.team how's this supposed to work then?
1 2
AnshCheck the official app. You can register a push token for users with your particular push endpoint and it should work for Graysky. Email me if you have issues at ansh [at] blueskyweb [dot] xyz
3 4SamuelWill do! Thanks :)
shreyan (wise)how does the push notification endpoint work? is it a lexicon or something unspecced
1 1AnshIt’s under notifications lexicon. Docs aren’t there yet unfortunately :/
1 2shreyan (wise)that's cool, do you have a quick summary of how it works?
1 1SamuelYou give the api a token, an appId, and a serviceDid. The service DID tells bsky where to send notifications, which you then send to devices using APN/FCM
1 1 2Samuelfor 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
shreyan (wise)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 3SamuelYeah that’s my understanding
1 2SamuelMy 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 1shreyan (wise)do you have a server that you could run Gorush on?
1 1Skeets AppWhat is the endpoint for? Will this be my „server“-endpoint that gets notified when there is a new push notification (and then delivers that push itself)?
Or does bsky send the pushes to e.g. APNS directly? I always thought device tokens were bound to the bundle-id and the push cert? 🤷♂️
2AnshThe code looks something like this
store.agent.api.app.bsky.notification.registerPush({
serviceDid: SERVICE_DID(store.session.data?.service),
platform: devicePlatform,
token: t,
appId: 'xyz.blueskyweb.app',
Notice how you can send an appId
2 5SamuelQuestion - api.bsky.app/.well-known/did.json lists the notification endpoint as just api.bsky.app - I’ve done the same for graysky.app but where do the requests actually go? Is there a specific path like /api/push?
https://api.bsky.app/.well-known/did.json
api.bsky.app
Skeets AppI was wondering....what would the serviceDid look like if I have a backend service that's running at
mybackend.com/pushService
?
1 2SamuelCheck out api.bsky.app/.well-known/...
You’d provide the backend url there. It then forwards the registerPush calls to it, at the same route
1 2SamuelHost a did.json file in your backend and then use did:web:mybackend.com as the serviceDid
1Skeets Appawesome! Where did you find this info???
1 1SamuelReading the atproto code (along with some help from @mary-ext.bsky.social)
2 1SamuelSo in summary your backend needs two routes
/.well-known/did.json
(Serves the DID document)
/xrpc/app.bsky.notification.registerPush
(Receives push tokens)
The rest is on you
1 2
YomamaHi Sam, sorry for a sudden bump to old post. I have made a route for those. I received a POST from bsky verbatim when I call registerPush. But still I don’t get any notifs for any activties I did to authed user.
1Skeets AppHave you out tried what will actually be sent to this endpoint? I'm looking for some way to authenticate accounts against my backend and was hoping this would be the way
1 1SamuelWhat you send to registerPush will be forwarded verbatim to your service
1 1AnshRight now the service DID is the Bsky App View but it can be your own service too if you want. We’ll just forward the data there
1 2Skeets AppOk, so the data flow is:
Bsky -> my backend -> APNS -> my app
Correct?
1AnshYeah if you set the serviceDID as your backend
1 1Skeets AppOk. So that can be just a URL?
What’s the data flow if I don’t set the service? I mean bsky cannot deliver data to APNS for my app without the push cert, can it?
1AnshHmm… I’ll have to double check. Check these files till then
github.com/bluesky-soci...
1 1Skeets AppThanks! I already went through that file a while ago. As far as I understand it hands off push notifications to gorush. gorush will probably be setup with the official bluesky app's APN certificate, which AFAIK means it will only be able to send push notifications to that specific app.
1 1AnshYes that is correct. Gorush has our own certificate.
However we designed this system to allow 3rd party devs to do notifications easily. Can you email me and we can chat more there?
2 4Skeets AppYou got mail :)
1