I can appreciate your concern and point of view, but I asked “so if I want to do this, how can I prepare to do it safely?” And your response was “just don’t, do this instead.” I can certainly seed, but that’s not what I’m aiming for. I am far more interested in creating systems and providing content. My time is…flexible. Suffice to say, the time concern is not going to be the roadblock.
I’d be more than a little interested to be pointed towards a guide, or even just a bullet point list, of good opsec considerations or tools for a project like this. I’ve got time and technical ability but don’t spend a lot of time thinking about these concerns. The last thing I want is to cause myself trouble I’m not ready for, but I’d like to make a significant contribution to the community, so I want to prepare adequately.
Any guides or lists you can think of?
Somewhat. They can certainly maintain a list of known IP addresses. Those IPs can be changed.
When they change, you as a user need to be able to find the new addresses. Whatever mechanism you can use, your ISP can likely disrupt too. For instance, they can DNS block the API that returns the list of possible endpoints (as sometimes happens to Proton where I live).
You can then counter by using private DNS. It’s a cat and mouse game.