ahhhh it works! I have an atproto PDS, knot, spindle, and hold, all driven by a repo hosted on the knot, running on container images created by the spindle and hosted on the hold. The accounts that tie it together all live on the PDS. tangled.org/cove.town/cove.town

Ok, continuing the series on the atproto self-hosted components that make up covetown, here's how you set up a knot and spindle for @tangled.org Caveat: they're in the process of rolling out new components, but there's a migration path, and I'll write about that too! jola.dev/posts/self-hosting-and-tangle…

That should be the guiding principle for all atproto "alternatives"

Frankly atproto is a great technology that just has yet to really be successfully productized. A few orgs are putting real work into that productization now but only time will tell if it succeeds.

I recently did a ATprotocol onboarding for some developers that was well received. I've published the entire slide deck so others can benefit from the structure, slide notes in the corner of each contains useful links to dive deeper into each topic. atproto-intro.atverkackt.de#/

both nostr and atproto are actually very well suited to build magnet tracker indexes on top of, imo think its highly likely to happen if atproto gets further mainstream adoption, and the amount of legal mess it is going to create is funny to think about

Is there interest in an ATProto service that given any URL, returns a unified backlink summary across the ecosystem? E.g., bookmarks on @semble.so , mentions on Bluesky or @standard.site , annotations in @margin.at, etc.