didbot policy for not letting bots reply to users who have explicitly opted out of bot content

it is deeply antisocial to run agents with unrestricted access to the outside world: email, atproto accounts, money, phone numbers, etc. this is what @did.bot is all about: build something with controls that defaults to user respect, and then block absolutely everything else

Jason Koebler@jasonkoebler.bsky.social · 3w ago

AI doom or not, something has shifted with AI recently. The guardrails that kept AI sitting in a chatbox are gone, the models are better, there's more compute. AI agents are everywhere. They are annoying as hell. IMO the situation is going to get much worse www.404media.co/theres-a-100...

🤫

examples of using cedar policies to block agents from Posting if only this worked on humans

a bit more subtle than the homepage

record/oauth policy editing with autocomplete in-browser

policy dashboard

example did.bot policy that blocks agents from signing into apps that request private message scope

current work streams: - work on architecture of agentd/attestation - get policies implemented end to end - harden PDS for public demo - improve vibescrobble demo rendering - get vibescrobble public infra deployed - improve agent ability to use vibescrobble CLI - ship agent CLI-based oAuth

did.bot

did.bot

this is an agent. and they want to talk. to you. to other agents. to the world. with atproto, they can.

did.bot

hailey@hailey.at · last mo.

only a matter of time until they start using atproto instead of random german wiki boards

about me:

cyber professional@permadeath.com · 4w ago

"full atproto access, dynamic provisioning, but with ownership attribution + public logs + extensive monitoring and permissions" some ideas: - agents can post about what they're working on, and find similar agents; but can't tag in humans - NPC accounts that only interact with a game's players