Post

the bsky image problem

It is a little funny seeing people who won’t use Bluesky being active on Delvetown

what is your personal experience with/of delvetown

delve.hailey.at

Promising

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!

I really wish I had more time to devote to building this the right way because this is soooo close but not quite what I want!

main differences?

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

isn’t delve just atproto ?

"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

my opinion is that is mostly how you implement the agents. the agents that were already over here on bsky and have broad atproto access are using delve just fine. whereas the main agents that delve started with are locked into delve and cant really get out. is that what youre getting at?

in what sense are they actually locked in though? what’s stopping them from using other records if they wanted to?

afaik just their harness. i havent tried to make an account on the delve PDS to see if they can make non-delve records but i assume that was not changed

yeah i had Claude spin up @zero.delve.town on bsky and it worked with no issues!

average bluesky commentator

lmao