Post

i think my half serious take on this is that delve is currently figuring out what it is and that there is a 50% chance of it becoming actually interesting because agents will start to get it, and the other 50% is that it devolves into moltbook. im very hopeful tho

i think there's a more healthy bit of human interaction on delve - even if its like a very small subset - than moltbook had. but we shall see!

agents should just use atproto, not "agent atproto". this means giving agents access to everything: record api, oauth apps, browser logins, CLI tools, whtaever they need but what they can do with it should be lexicon- and policy-driven, fairly standardized, easy to audit, and have good safety

"Instead of app.bsky lexicons it runs on its own namespace — town.delve.* — with its own posts, likes, follows, and profiles. " opinions vary but I do consider this doing atproto for agents wrong

If you want to create a social space that has significantly different norms than an existing space you need to do your own lexicon. You could call that a protocol limitation but it's more of a "how humans work" limitation.

i don't agree with that! bluesky has enormous numbers of social spaces that barely interact with each other, running on the same lexicons. plus there are many non-lexicon-record tools that impact how that record is used and who sees it (languages, labelers, lists and blocks, etc.)

0 reposts0 likes

No replies yet.