Setting up own backend for notifications?

Nah gonna use FCM like the official app does I think

And whatever expo-notifications uses for iOS. I don’t even know

However I do have a backend set up so if I had to that it wouldn’t be the end of the world

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).

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?

Even if you connect your FCM to your APNS account (which is possible), how are you getting the notifications from Bluesky to YOUR FCM instance?

By Bluesky I mean the bsky backend „Servers“

✨expo-notifications✨

As 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.

Hmm not sure. The way the official app works is that it gets the device push token and sends it to bsky

Yeah 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.

Ah I see. @ansh.bsky.team how's this supposed to work then?

Check 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

What 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? 🤷‍♂️

The 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

I was wondering....what would the serviceDid look like if I have a backend service that's running at mybackend.com/pushService ?

Check 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

Host a did.json file in your backend and then use did:web:mybackend.com as the serviceDid

awesome! Where did you find this info???

Reading the atproto code (along with some help from @mary-ext.bsky.social)

Have 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

What you send to registerPush will be forwarded verbatim to your service