Samuel
@samuel.fm
let's go. steps 1 & 2 of notifications (getting push tokens from the device and receiving events from the firehose) is working
1 1 11
Samuelnow we just need step 3 (filtering out mutes & blocks 🙃) and step 4 (sending them!)
2 6Samuelthanks for the reference code @haileyok.com, made the firehose part 10x easier
6
Michel BestaatWhat ya doing?
1 1Samuelapp.bsky.notifications.registerPush to send push tokens to my server
1 2Michel BestaatOooh. 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 1Samuelyeah 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 4Samuelthen you have to read the firehose to figure out what to send to that token. It’s a lot!
1 2Michel BestaatHave fun!
1Michel BestaatI see. My atproto tinkering got already out of hand. Now I need a server. 😅
We'll see.
1 3SamuelYep 😅 this is by far the roughest part I’ve come across tbf, clearly needs improving on the protocol side
1 3Michel BestaatThe 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 1SamuelOh 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)
2Michel BestaatBut you won't be bored during the holidays.
1