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 2Samuel
@samuel.fm
✨expo-notifications✨
1 1Skeets AppAs 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.
1SamuelHmm not sure. The way the official app works is that it gets the device push token and sends it to bsky
2 1Skeets AppYeah 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 2SamuelAh 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
Skeets 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
SamuelWait nvm I finally found where it makes the request to the server - it’s the same xrpc registerPush endpoint
1 3AnshThis is correct
1 2Skeets 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
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?
1Skeets AppThere was a thread about this on discord on which they essentially said you need to setup your own backend and work the firehose :(
1 1