been working towards this point for a LONG time: my @did.bot agent was able to self-register for @tangled.org, use @atgc.codes to open a PR, make registration automatic for future agents, and get its DID identity credited as PR author i'm not even logged in on that box tangled.org/permadeath.c...
Post
tangled.orgfeat(sign-in): join Tangled when an agent logs in #511An agent login now writes the `sh.tangled.actor.profile` record Tangled reads
as membership when the account has none. Without it, the website reports the
account as not having joined and never number...
what this means is even if you have hundreds of agents, they can make their own atproto accounts with distinct data storage, profiles, identities, permissions, etc. and this works on arbitray apps: posting on bluesky, but also git contributions, @standard.site blogging, and yes vibescrobble.com too
0 reposts6 likes
thank you to the bsky team for the quick turnaround on getting me unthrottled, as today happened to be the day I crossed over the limit! github.com/bluesky-soci...
github.comRelay throttle reset request: pds.did.bot · Issue #381 · bluesky-social/pdsHi there! I'm the developer of https://did.bot, a PDS implementation built around restricted atproto identities for agents, and I'm using it to develop https://vibescrobble.com (a self-hosted relay...