For anyone else who needs to hear this,

Hi,

I don’t have a mastodon to reply directly to you.

But i have had some issues with content being taken down by VPS providers as well.

What I’ve found works well is to use a VPS provider that the public is unaware of. And for some time I had used OVH based on the unlimited bandwidth and the reasoning that Wikipedia and Julian assange (who have far more enemies than I ever will) were using OVH.

I don’t know if that’s true any more because I subsequently moved my content to ENS and IPFS.

Anyway regardless of where your content is actually hosted or lives,

What I had done was turn my “real” servers into content origins , which were concealed form the rest of the world and lock it down in the firewall so it could only be reached by disposable squid proxy servers with a 10-liner config file

Then I pointed DNS , cloud flare etc at the squid nodes

And couldn’t care less if they were taken down.

Because I could deploy new ones in minutes elsewhere.

I didn’t have “bad content”, just ruthless business competition that kept coming at me like Tonya Harding.

And I’m sharing because your content didn’t seem too offensive either.

In the front end VPS nodes you’d just put the real address of your content as the remote origin.

And then nobody but you will ever know where it is.

Then generally your hosting company shouldn’t be aware of what it is either unless they’re snooping around in your files, and if they are, hell with them too.

You’re welcome to pass this along as a remark on avoiding censorship, or keep it to yourslelf as proprietary information I don’t mind. Let me know if you want or need an example squid conf. It’s seriously 10 lines at most and many examples found on google.