Event JSON
{
"id": "0fa04e9b9ea05295fb001df0d9056c674bac20b2e8f327d2c1adec4d05332dae",
"pubkey": "89ef92b9ebe6dc1e4ea398f6477f227e95429627b0a33dc89b640e137b256be5",
"created_at": 1737545749,
"kind": 1,
"tags": [
[
"e",
"1eb6ab8edd22a43a12f686b0fb818b1a451f754692ec8accf3be8deef6df9e78",
"wss://bostr.bitcointxoko.com",
"root"
],
[
"p",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa",
"",
"mention"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"",
"mention"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"r",
"wss://communities.nos.social/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://purplepag.es/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.mostr.pub/"
],
[
"r",
"wss://relay.nos.social/"
]
],
"content": "Which IP is the one misbehaving? At nos.social, we have a couple of scrapers. One respects rate limits, though we might need to adjust the backoff settings. The other one is more likely to be causing the issue, as we haven’t had time to implement rate-limiting there yet. This could be a good wake-up call for us to prioritize that.",
"sig": "812b3122ca05ac401ca24c60397fbbf879da0beb6034e9ce11f0053706a425065475bcea9428c80d15c822187f61b6db62bffa0e0babfd5dd974d366cbfeb0b6"
}
