npub1sqr0yfj6d8tyxxesvq3dghmzwqd0dgzs4s9jrklnd5gg8hlg0t2sclqs4m (npub1sqr…qs4m)
Speaking for myself, I appreciate the clarification and short explanation, as otherwise this can be perceived quite simply as an attack with no true proper reason.
One question, though. Yes, I acknowledge that information on my instance is public and I do not intend to intensely restrict access to it (as there is quite simply no good reason or way to do so without extensive compromises), but this does not explain why the bot needs access to either the public timelines or specific user accounts if it is just searching the vaguely-identified "content moderation policies." For convenience, I'm not going to question the relevance or possibility of moderation in a federated network, as it's quite simply irrelevant right now.
There is a lot of ambiguity in that regard so rather than making assumptions, I'd rather ask: what's up with that? How is the information there relevant? (and also, why are single-user instances, like mine, that only have very few users, relevant to this as well, and is there a way to opt out?)
atlas /
npub125…vxt3h
2023-12-06 15:12:01
in reply to nevent1q…ezyu
Author Public Key
npub1250kzt5eet2jynh7qjlw9h2x4peum6vzex55fvcw2zcu5vr5me8suvxt3hPublished at
2023-12-06 15:12:01Event JSON
{
"id": "1efbd9d8d33a575a4d9d57ca0988bfec989a1b0e71531bf5025ef132cdd9d3ac",
"pubkey": "551f612e99cad5224efe04bee2dd46a873cde982c9a944b30e50b1ca3074de4f",
"created_at": 1701871921,
"kind": 1,
"tags": [
[
"p",
"8006f2265a69d6431b306022d45f62701af6a050ac0b21dbf36d1083dfe87ad5",
"wss://relay.mostr.pub"
],
[
"p",
"3a59b71261ab5ff49b1a752ee5f64b32f57a41e45cd8b5411523e6124fe561d3",
"wss://relay.mostr.pub"
],
[
"e",
"5ee5c832e7a66488e570a457c7c00be4fd4d68980d27af86d1d5e416b18c983b",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://thonkbox.rightmouse.click/objects/3983aac8-63f9-4463-961d-9e91b312a758",
"activitypub"
]
],
"content": "nostr:npub1sqr0yfj6d8tyxxesvq3dghmzwqd0dgzs4s9jrklnd5gg8hlg0t2sclqs4m\nSpeaking for myself, I appreciate the clarification and short explanation, as otherwise this can be perceived quite simply as an attack with no true proper reason.\n\nOne question, though. Yes, I acknowledge that information on my instance is public and I do not intend to intensely restrict access to it (as there is quite simply no good reason or way to do so without extensive compromises), but this does not explain why the bot needs access to either the public timelines or specific user accounts if it is just searching the vaguely-identified \"content moderation policies.\" For convenience, I'm not going to question the relevance or possibility of moderation in a federated network, as it's quite simply irrelevant right now.\nThere is a lot of ambiguity in that regard so rather than making assumptions, I'd rather ask: what's up with that? How is the information there relevant? (and also, why are single-user instances, like mine, that only have very few users, relevant to this as well, and is there a way to opt out?)",
"sig": "667111a37987073284449f77f0e6fea524a849daa33486c9a8d568f459d75d473c4b12fd384d7789a4c40710b6c1e1d0c3bf6382b6f4a32a5184418b20eceac7"
}