Vaghrad (npub1cxy…9d6t) Fe₂🦀₃⋅H₂🦀 ( 10,200 / 28,000 ) (npub1y6t…9wl9) cassidyclown (npub1zhj…kmgu) Yeah, especially since they seemed to probe it, like they'd hit an account that got banned, then immediately go to the registration page. For a while, there were so many of them searching for a specific Pawoo account that I killed off any IP that searched for that account (only one post had federated to FSE, picture of a child and a mega.nz link from an account that had already been banned from Pawoo, so I made an educated guess; I killed that account and anyone that had interacted with the post). I think the only time I ever *automatically* killed IPs just for a search term, usually it would ping me and I'd look.
The nice thing about them is they can be analyzed after the fact for diagnostics. The bad thing about them is they can be analyzed after the fact for feds. The compromise was I'd keep just two days and change around usually, enough that I could spot problems but not enough that I was creating an incentive to send me a subpoena or show up with a warrant. Sometimes I'd keep around aggregates (mostly performance stuff, or when I was trying to figure out why I got a $500 bandwidth overage bill) or excerpts (e.g., if something weird was going on, I'd grep the file for the weirdness and squirrel it away so if it happened again, I could check if it was the same thing or something else).
p /
npub1nj…psg7d
2024-03-09 08:11:19
in reply to nevent1q…zg93
Author Public Key
npub1nj0l0jxtuhwksd352wlwgepkvp03da2pmunemtefcau09k7nlk6shpsg7dPublished at
2024-03-09 08:11:19Event JSON
{
"id": "4807b5ce7a354fc15b4e8436341841de6e0b10adcaf9c2c19724f55d44581dbb",
"pubkey": "9c9ff7c8cbe5dd68363453bee46436605f16f541df279daf29c778f2dbd3fdb5",
"created_at": 1709971879,
"kind": 1,
"tags": [
[
"p",
"c189803d96323b30fb9fdbea2e8a1c9dd473db5c7b63b9c5e23429d510624034",
"wss://relay.mostr.pub"
],
[
"p",
"26976d1f3f3270311c86a59315751d66bd770aa35a929529271fca721afee1af",
"wss://relay.mostr.pub"
],
[
"p",
"15e47e47a1d7b89fc2a3056b659794dfc15d4bba34b3f8a85d576563a3d4ca67",
"wss://relay.mostr.pub"
],
[
"e",
"aa2dd4469f4fe80b4e09a017bd6059b00d27ca00e7f463aa3fbf1ec59e1ae6ce",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://shitposter.club/objects/88c59e80-6931-4da7-8ae4-4d50b239b6ce",
"activitypub"
]
],
"content": "nostr:npub1cxycq0vkxganp7ulm04zazsunh288k6u0d3mn30zxs5a2yrzgq6qkv9d6t nostr:npub1y6tk68elxfcrz8yx5kf32agav67hwz4rt2ff22f8rl98yxh7uxhsx69wl9 nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu Yeah, especially since they seemed to probe it, like they'd hit an account that got banned, then immediately go to the registration page. For a while, there were so many of them searching for a specific Pawoo account that I killed off any IP that searched for that account (only one post had federated to FSE, picture of a child and a mega.nz link from an account that had already been banned from Pawoo, so I made an educated guess; I killed that account and anyone that had interacted with the post). I think the only time I ever *automatically* killed IPs just for a search term, usually it would ping me and I'd look.\n\nThe nice thing about them is they can be analyzed after the fact for diagnostics. The bad thing about them is they can be analyzed after the fact for feds. The compromise was I'd keep just two days and change around usually, enough that I could spot problems but not enough that I was creating an incentive to send me a subpoena or show up with a warrant. Sometimes I'd keep around aggregates (mostly performance stuff, or when I was trying to figure out why I got a $500 bandwidth overage bill) or excerpts (e.g., if something weird was going on, I'd grep the file for the weirdness and squirrel it away so if it happened again, I could check if it was the same thing or something else).",
"sig": "ddd3740ac32e68433daa3a7570f8f93f489513b5ef568e84bdf3b434dc23420fe4766ef75d0f71432483821e9ad33efff8a10c0e8b172feae2b38d23d73edf10"
}