someone on Nostr: I have no time to track people's usage but yeah if a relay wants to know more they ...
I have no time to track people's usage but yeah if a relay wants to know more they could. Didn't even write the scripts to delete events. So all the events are filling up memory and disks. Sometimes people ask manual deletion of events and I don't reply, I have no tools to do that. I have to login and delete the notes using command line.
My relays are pretty low maintenance. I rarely login and do stuff. Thanks to really solid strfry implementation it runs without problems.
I limited the logs to about 4 GB. So old logs are automatically deleted. This 4 GB limit only allows recent logs to be kept. I keep those logs for any attack from an IP that may happen towards the relay. Maybe I could lower that number more since Hetzner DC seems to be handling traffic floods really well. This setting also means the drives does not fill quickly with logs. So even less maintenance for me.
nos.lol does not keep IP information in logs for a long time (only recent activity which fits the 4 GB limit above). nostr.mom has a very old write policy script from initial days of Nostr. Back then before strfry I was using Cameri's relay software and needed a necessity to store IPs to be able to do IP-ban the attackers. Nowadays those don't seem to happen.
There you go, some transparency for you.
It's not just the relays you use. It's ALL relays that are publicly writeable. If you care about privacy, use a VPN or TOR.
nevent1q…e9az
Published at
2025-05-01 18:24:03Event JSON
{
"id": "cf602eee42ddbb7895bedcbc7108cfb115f955edd0d5d486c74456ea165ecd76",
"pubkey": "9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1",
"created_at": 1746123843,
"kind": 1,
"tags": [
[
"q",
"c522689c0b45ff0eb20515384dc4d53ad14d475efb99cfef6edf6d3b4e0bf590",
"",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"",
"Derek Ross"
]
],
"content": "I have no time to track people's usage but yeah if a relay wants to know more they could. Didn't even write the scripts to delete events. So all the events are filling up memory and disks. Sometimes people ask manual deletion of events and I don't reply, I have no tools to do that. I have to login and delete the notes using command line.\n\nMy relays are pretty low maintenance. I rarely login and do stuff. Thanks to really solid strfry implementation it runs without problems.\n\nI limited the logs to about 4 GB. So old logs are automatically deleted. This 4 GB limit only allows recent logs to be kept. I keep those logs for any attack from an IP that may happen towards the relay. Maybe I could lower that number more since Hetzner DC seems to be handling traffic floods really well. This setting also means the drives does not fill quickly with logs. So even less maintenance for me.\n\nnos.lol does not keep IP information in logs for a long time (only recent activity which fits the 4 GB limit above). nostr.mom has a very old write policy script from initial days of Nostr. Back then before strfry I was using Cameri's relay software and needed a necessity to store IPs to be able to do IP-ban the attackers. Nowadays those don't seem to happen.\n\nThere you go, some transparency for you.\n \nnostr:nevent1qvzqqqqqqypzq0mhp4ja8fmy48zuk5p6uy37vtk8tx9dqdwcxm32sy8nsaa8gkeyqqsv2gngns95tlcwkgz32wzdcn2n452dga00hxw0aahd7mfmfc9ltyqz9qe3c",
"sig": "1624cd1874fdc13b3b16c7578bb7405c738fc6b1b48f2a8fb8e29a76e59a845d11eaa7190928588c27e0c006adcee4c9a9dd6affa958d1017a782c39b1b79d3c"
}
