There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.

Found a conventional use for atproto (replacing high school state associations/athletic conference/school sports websites) the other day and built a spec because I couldn't help myself. it's live but I'll share a blog post about it before sharing

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.

i really wish atproto.com had a "Understand ATProto as a regular person" and it used zero diagrams and just had plain language explaining things

adding social features to our websites will accelerate atproto adoption faster than building pure atproto apps

The reason I've become such a @standard.site stan is because it's forming into the first real multi-service parallel ecosystem on atproto that can survive on it's own without the need of the @bsky.app lexicons and infra

my hot take is that @semble.so is on par with traditional search engines for atproto related topics (and it's only curated by people!)

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.