Hmm not sure. The way the official app works is that it get…

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

deck.blue 26 Oct 2023

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?

2 2

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.

Samuel

@samuel.fm

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

2 1

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

3 4

shreyan (wise)26 Oct 2023

Will do! Thanks :)

how does the push notification endpoint work? is it a lexicon or something unspecced

It’s under notifications lexicon. Docs aren’t there yet unfortunately :/

shreyan (wise)26 Oct 2023

that's cool, do you have a quick summary of how it works?

You 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 2

https://api.bsky.app/.well-known/did.json

for example did:web:api.bsky.app, which you can see here api.bsky.app/.well-known/did.json

api.bsky.app

shreyan (wise)26 Oct 2023

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 3

Yeah that’s my understanding

1 more reply

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

2 5

https://api.bsky.app/.well-known/did.json

Question - 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?

api.bsky.app

1 3

Wait nvm I finally found where it makes the request to the server - it’s the same xrpc registerPush endpoint

This is correct

But to be clear it’s up to me to find the posts myself via the firehose, right?

shreyan (wise)27 Oct 2023

yikes. i don't know if i like that.

Skeets App 31 Oct 2023

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

Samuel 31 Oct 2023

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

Samuel 31 Oct 2023

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

Skeets App 31 Oct 2023

awesome! Where did you find this info???

Samuel 31 Oct 2023

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

2 1

2 more replies

Right 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

Ok, so the data flow is: Bsky -> my backend -> APNS -> my app Correct?

Yeah if you set the serviceDID as your backend

Ok. 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?

Hmm… I’ll have to double check. Check these files till then github.com/bluesky-soci...

Thanks! 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 more reply

There was a thread about this on discord on which they essentially said you need to setup your own backend and work the firehose :(