I had a little trouble getting my head around how multiple publications on the same domain would work with @standard.site, so I wrote up how I did it for @codetv.dev in case it helps anyone else

We're thinking about publishing a compendium of #ATScience projects submitted to the workshop (incl abstracts, preprints and published works) - @aaronstevenwhite.io could @chive.pub potentially support that use case?

After reading about ATProto stuff this morning I realised that one possible future for science publishing, within something like @atproto.science, is that every scientist becomes their own journal. The key realisation is that a paper published to my own PDS can be published in many journals.

Super cool! Imagining how something like this could be used for @atproto.science "journal" publishing

atproto'd my website a bit further (beyond the @standard.site integration): 1) added a "Right now" box on the homage that pulls in all kinds of atproto activity like @bsky.app posts, @popfeed.social film ratings, @bookhive.buzz reads, @tangled.org repo's etc.

What if there was an atproto microblogging tool where you could tag your posts and every tag is also its own subdomain of your handle, so people can either follow your main (which reposts everything from its subdomains) or any of your subdomain handles (to only follow particular tags)

What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?

It doesn't have to be ATProto. Local agencies should be publishing RSS feeds (or another governed and certified open format) with critical information, and all the different platforms can translate that into posts.

New Feature: Collections on Standard Reader. Curate articles from across the network into magazine editions. Include your editorial intro, notes on each piece, a closing statement and a theme. Publish as a series readers can follow. Tell a story. Check out the first one 👇

Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.

Tried to explain a bit of the use case of @varsityapex.com and why it made sense to integrate ATproto features. A full fledged site would make even more use, for the demo just opted to make records of non-score items. Tour: varsityapex.com/tour Was fun to explore the problem space a bit

Have had this conversation more than once that essentially having to buy a domain and host a distinct machine for every single idea to be a poc in ATProto sux