Oh it’s not even that. It just forwards it to a server (in…

Samuel 22 Dec 2023

let's go. steps 1 & 2 of notifications (getting push tokens from the device and receiving events from the firehose) is working

Samuel@samuel.fm· 22 Dec 2023

thank you Josh!

1 1 11

Samuel 22 Dec 2023

now we just need step 3 (filtering out mutes & blocks 🙃) and step 4 (sending them!)

2 6

Michel Bestaat 22 Dec 2023

What ya doing?

1 1

Samuel 22 Dec 2023

app.bsky.notifications.registerPush to send push tokens to my server

1 2

Michel Bestaat 22 Dec 2023

Oooh. Are you sure you can pull that off? Coincidentally I saw a reply from Paul this morning on my question on that. He told me that push notifications cannot be sent to third party apps (in the atproto github how to discussions)

1 1

Samuel 22 Dec 2023

yeah so their backend cannot send it to our apps. but we can make our own backends (which is what @skeetsapp.com does). simply change the serviceDid to your own service (i.e. did:web:graysky.app, which then has a DID document at graysky.app/.well-known/... pointing to my API

2 4

Michel Bestaat 22 Dec 2023

I see. My atproto tinkering got already out of hand. Now I need a server. 😅 We'll see.

1 3

Samuel 22 Dec 2023

Yep 😅 this is by far the roughest part I’ve come across tbf, clearly needs improving on the protocol side

1 3

Michel Bestaat 22 Dec 2023

The registerPush seems only some very light sugar coating around Google's Fire Cloud Messaging. In understand this is not your top prio when building a new protocol.

2 1

Samuel

@samuel.fm

Oh it’s not even that. It just forwards it to a server (in the official app’s case, the AppView, which then figures out what to send and sends it to APN/FCM)