this toml-in-git could have been atproto records #1

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.

But 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:

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
you'd get more direct attestation/authenticity linked to a publishing account
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
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

i can see the appeal in these decisions being records in a repo tbh but i agree with fig, just having these live in git rn seems like an easier lift

also agreed on this point

or microcosm relays: i won't be automatically applying changes from this repo, but pulling them in on a routine -- what i want is a tool that essentially diffs what my relay's settings are against it, and lets gives me a yes/no/modify options when there's a new change. i think i probably want to make that info publicly available too (how microcosm relays differ from consensus here).

i think initially i just wanted to auto-apply any decision that was made but there could be (i don't think there will be) some decisions i disagree with and would want to have the freedom to make that choice

Configure Feed

Configure Feed