Allow removal from directory #83

New issue

Closed

opened 2021-12-30 04:18:33 +01:00 by zackman0010 · 4 comments

zackman0010 commented

2021-12-30 04:18:33 +01:00

I would like the ability to remove my server and users from the directory. The description says it is opt-in, but my server had it enabled by default when I installed. I didn't intend for the server to be global, as I was making something private for my family and hosting it on my home network.
After my server was added, I began getting a lot of requests from other Friendica servers pinging mine, drowning out my server and preventing me from even accessing it locally. I don't have the resources to keep up with the kind of traffic I was seeing. My logs list some IPs hitting me 10s of thousands of times.
Unfortunately, there doesn't appear to be a way to remove my server from the directory, at least not one I can find.

I would like the ability to remove my server and users from the directory. The description says it is opt-in, but my server had it enabled by default when I installed. I didn't intend for the server to be global, as I was making something private for my family and hosting it on my home network. After my server was added, I began getting a lot of requests from other Friendica servers pinging mine, drowning out my server and preventing me from even accessing it locally. I don't have the resources to keep up with the kind of traffic I was seeing. My logs list some IPs hitting me 10s of thousands of times. Unfortunately, there doesn't appear to be a way to remove my server from the directory, at least not one I can find.

MrPetovan commented

2021-12-30 11:02:58 +01:00

Owner

Thank you for reaching out and sorry for the inconvenience.

I can manually mark your domain as ignored on the official Friendica directory, however it won't prevent remote servers that already discovered your domain from continuing to ping it.

At this point the easiest way for you to avoid unwanted traffic is to change the domain name your node is accessible at after disabling directory listing in the Admin. A minor change (a single different letter) is enough. Don't forget to update the relevant setting.

We usually don't recommend to do that because it severs all ties to remote servers and contacts but it seems like that's exactly what you want.

There's also a setting disabling all federation that you can enable. If you are afraid the new domain will be registered in the directory before you get to the setting, here's my suggested walkthrough:

Disable the background worker, as it is the only way to register your domain in the directory.
Go through the settings, disabling anything federation and directory related.
Change the domain in the config file.
Update your DNS and web server configuration to point the new domain to your existing install.
Re-enable the background worker.

Thank you for reaching out and sorry for the inconvenience. I can manually mark your domain as ignored on the official Friendica directory, however it won't prevent remote servers that already discovered your domain from continuing to ping it. At this point the easiest way for you to avoid unwanted traffic is to change the domain name your node is accessible at after disabling directory listing in the Admin. A minor change (a single different letter) is enough. Don't forget to update the relevant setting. We usually don't recommend to do that because it severs all ties to remote servers and contacts but it seems like that's exactly what you want. There's also a setting disabling all federation that you can enable. If you are afraid the new domain will be registered in the directory before you get to the setting, here's my suggested walkthrough: 1. Disable the background worker, as it is the only way to register your domain in the directory. 2. Go through the settings, disabling anything federation and directory related. 3. Change the domain in the config file. 4. Update your DNS and web server configuration to point the new domain to your existing install. 5. Re-enable the background worker.

MrPetovan commented

2021-12-30 12:08:32 +01:00

Owner

Opened an issue over on the official Friendica repository to make sure your scenario can't happen again.

Opened [an issue over on the official Friendica repository](https://github.com/friendica/friendica/issues/11125) to make sure your scenario can't happen again.

zackman0010 commented

2021-12-30 16:56:35 +01:00

Author

Unfortunately I'm not able to change my domain name, as I only own the one. However, I did go ahead and IP block the worst offenders from my firewall. 5 IPs had each pinged >10,000 times, and another 6 >2,000. I've disabled the federation now and will just keep an eye on my performance to watch for any more blocks I need to perform.
If you could still go ahead and mark my domain (sistrunk.dev) as ignored, though, I would appreciate it. Thank you!

Unfortunately I'm not able to change my domain name, as I only own the one. However, I did go ahead and IP block the worst offenders from my firewall. 5 IPs had each pinged >10,000 times, and another 6 >2,000. I've disabled the federation now and will just keep an eye on my performance to watch for any more blocks I need to perform. If you could still go ahead and mark my domain (sistrunk.dev) as ignored, though, I would appreciate it. Thank you!

MrPetovan commented

2021-12-30 18:16:27 +01:00

Owner

May I suggest using a sub-domain for your one domain? You're free to create as many sub-domains as you want for it. For example, you can create friendica.sistrunk.dev through DNS configuration and point it to your existing node.

I went ahead and marked your domain as ignored in the directory.

May I suggest using a sub-domain for your one domain? You're free to create as many sub-domains as you want for it. For example, you can create `friendica.sistrunk.dev` through DNS configuration and point it to your existing node. I went ahead and marked your domain as ignored in the directory.