joeross🍁me on Nostr: 👇Really important. Like many “protection from abuse” systems in the U.S., ...
Published at
2023-07-06 21:18:20Event JSON
{
"id": "ea3df0a5f59417859eae7eb6669b7b06d24f70cf2e14e50c388ae064a6634331",
"pubkey": "4dbcf6d7528ee21c71f3c0b6a6e091a492c1e727734b0366591364c7fbfab338",
"created_at": 1688678300,
"kind": 1,
"tags": [
[
"p",
"d4d23dfa0b809bc3eb1884e8237967e592c6318d34e798231c6c7b55723bad52",
"wss://relay.mostr.pub"
],
[
"p",
"3a357a10b33257f231aba8f6dadeced9fed17dd79a543b45f8e57410fee9f672",
"wss://relay.mostr.pub"
],
[
"t",
"fediverse"
],
[
"mostr",
"https://mastodon.social/users/joeross/statuses/110669221099493631"
]
],
"content": "👇Really important. \n\nLike many “protection from abuse” systems in the U.S., waiting until someone has been harmed to implement protections is a deeply flawed approach at best.\n\nI don’t know much about how Mastodon/broader #fediverse work, but is it possible to develop shared denylists?\n\nI know this is something AT protocol/Bluesky builds in, but I think their method is problematic: https://atproto.com/blog/block-implementation\n\nCan it be done without being public?\n\nFrom: nostr:npub16nfrm7stszdu86ccsn5zx7t8ukfvvvvdxnnesgcud3a42u3m44fqlenmp8\nhttps://mstdn.social/@kissane/110669097973407209",
"sig": "1f8a99369fe6115e33c0cd21986d51bb3ef8375964a6298197a86199b87c8d6213bccbc3c8074fba5bcff6c81dc15c08ff51215f14d6d389d58ad7db0bbc6568"
}