[@zzstoatzz.io](

Bluesky Social

nate (@zzstoatzz.io)

oss @prefect.io + atprotobro ‣ plyr.fm ◦ zzstoatzz.io ◦ status.zzstoatzz.io ◦ tangled.org/zzstoatzz.io yooper → umich → chicago

) is cooking [status.zzstoatzz.io/@plyr.fm](

status

) [@plyr.fm](

Bluesky Social

plyr.fm (@plyr.fm)

music on atproto (by @zzstoatzz.io) ✶ plyr.fm ✶ plyr.leaflet.pub ✶ https://status.zzstoatzz.io/@plyr.fm ✶ tangled.org/@zzstoatzz.io/plyr.f...

)

The core of the Atmosphere is using the PDS to store user's records, just like desktop apps use the filesystem. Desktop apps interoperate using files. Atmosphere apps interoperate using repo records. That's the ethos that I highly doubt will ever change.

Nerding out about the question of whether the client or the server should be the one who speaks to the PDS [The politics of purely client-...](

The politics of purely client-side apps - Paul's Leaflets

There's a surprisingly nuanced discussion in development about the political economy of clients and servers in the Atmosphere

)

You can't say you're buying something for "pennies on the dollar" anymore. Nobody will know what you mean. "Pennies!?" they'll say. "OK boomer" they'll say.

Don’t fall for the social posts about the aurora this is a bird box situation, they’ve all got bird box