at://did:plc:44ybard66vv44zksje25o7dz/sh.tangled.repo.issue/3miwm5d3hmh22

Back to Collection

Record JSON

{
  "$type": "sh.tangled.repo.issue",
  "body": "TBC I think this is a great start and don't want to give anybody a hard time. It's also nice to have a clear discussion spot, like these issues.\n\nBut it might be cool if PDS infra actions happened \"on protocol\", in the form of records-in-repos? I hadn't really thought about this until just now. Unstructured thoughts:\n\n- account-level mod decisions shouldn't be so public, but transparency and enumerability are probably good for infra-level decisions? and it would always be possible to simply not publish actions if needed\n- you'd get more direct attestation/authenticity linked to a publishing account\n- sync mechanisms would make it possible both to backfill from multiple sources, and to get real-time-ish notification. you could potentially delegate trust to communal authorities (configured by DID) and take automatic actions\n- another option would be labels, where the subject of the label is either a service DID, or an HTTPS URL. label values could be `blocked`, `vetted`, `legit-100k` (for that number of accounts), etc",
  "createdAt": "2026-04-07T20:21:17Z",
  "repo": "did:plc:ljtzpynwgaltprhfmo5c6bcv",
  "title": "this toml-in-git could have been atproto records"
}