Post

jared
@awarm.space

been wanting something like this! I think the killer thing to get right is new user onboarding vs existing user. Will try and set it up in a test app sometime soon!

Lyre Calliope 🧭✨
@captaincalliope.at

First thought looking at this: Apps should somehow be able to declare themselves as channels. Possibly by deploying a small library in their apps to make them a passthrough channel so notifications go directly to user instead of through their app servers. Privacy, good UX, clear value prop for devs.

atmo.pubatmo.pub — notifications for the atmosphereLet any AT Protocol app send you notifications — via web push, Telegram, email, Bluesky DM, or a webhook — all kept in one inbox. Every app asks permission; revoke anytime.
Guido X Jansen
@gui.do

Q2: any way to mark a notification as non-routable for legal/security purposes? Q3: can we query "is this user atmo-subscribed and to which categories?" so we can show meaningful UI inside Sifa?

Guido X Jansen
@gui.do

Re: subscriberChanged: it's binary (enabled/disabled for the whole app), which is fine for delivery but means we can't reflect per-category mute state back in our own UI, or skip work for categories the user has routed to nothing.

flo-bit
@flo-bit.dev

you can get per-category mute state with `getCategories` but you need an active user token (see the other answer too), though more webhooks for apps is on idea so you dont have to poll when sending notifs

flo-bit
@flo-bit.dev

generally i was thinking apps just send all their notifications always and dont need to care about mute state though (seem easier for apps?)

flo-bit
@flo-bit.dev

A2: what are non-routable notifications? feels like for that you'd have your own relay and then completely control routing A3: yes, see #6 here: docs.atmo.pub/docs, each app can read and write the categories they serve and where those go (the example sender app has those settings too)

Guido X Jansen
@gui.do

Q: any thoughts on pricing or how you're planning to keep the hosted atmo.pub running long-term? trying to decide if I'd integrate the hosted version or self-host the relay from the start

flo-bit
@flo-bit.dev

no long term plans yet, in the end this is one of those parts that somehow needs community funding (like microcosm, shared appviews, relays), but feels like this part should be very cheap to run even with lots of users with the possible exception of email notifications

flo-bit
@flo-bit.dev

as a sidenote regarding relays: you can always send notifications to multiple relays though currently the atmo.pub app is only connected to my relay, so if users want to get push notifs from there you need to use my relay

atmo.pubatmo.pub
flo-bit
@flo-bit.dev

once permissioned data is here we can move stuff over to that though and then any relay and any notification app should be able to work together too (as long as they read from the same space type)