Atmosphere social client apps should make it easier to broadcast beyond the protocol. Ex. In-app mirroring tools for Threads, X, and other microblogging platforms. As well as having post scheduling. Let people share across the social internet, but make sure ATproto feels like home base.

oh i forgot to mention in my talk, but some of us small indie relay operators are getting together to make @firehose.club so we can share network limit bumps and bans and build some shared tooling. we can go further together <3

running your own relay and such is in theory good but how you do you keep track of all the pds out there without going back to the Bluesky relay or someone's project that generates a list on a GitHub repo

Q for Atmosphere gurus: I have many Atmosphere blogs (debbieohi.com/links/). Is there any way I can point people to one page via simple link, where they can see most recent updates in all my ATblogs *without* having to sign up for an app & without having to open up each of my blogs? 🤞🏽

Thinking about rebuilding @val.town / @smallweb.run on top of atproto, with an architecture inspired by @tangled.org. Every user can bring it's own runner, but the there is a federated appview for social stuffs (likes, follow, ect...).

FWIW the most cohesive big picture atmosphere experience I've gotten so far is getting a push notification from stream.place, logging in to the stream, and chatting with oomfs. it's perfect

two relays, three jetstreams, two plc mirrors, created lightrail (running one instance, several others deploying it), spacedust, constellation and slingshot in HA configs serving hundreds of apps, ufos, firehose compare, pds debugger, a bunch of demos, hubble-mini already mirroring every indie pds,