Okay, so you built the server and are colocating it somewhere? Do you own the connection and bandwidth yourself? There's a point of failure.
I own the software
Then you might want to disable XML-RPC (or just pingbacks) in WordPress so that you stop leaking your hardware IP. I'd probably audit the other plugins and/or themes you're using (since you apparently "own" them, wtfever that means) so they don't leak as well. CloudFlare is nice, but it's not magic.
only I know where the server sits
See the above.
Once moved to Epik (like bitchute), it will take a court order to remove content, which I will fight in person till the bitter end.
lol it's not the DMCA that is going to deplatform you. It's going to be ISP related, or payment related. Ask NewProject2.
Explain a bit about the payment issue you forsee. I am self funding this and have the means to privately fund it for years to come without needing external income. Outside of that, BTC can be used for lightweight payment processor bypass, but it shouldn't be necessary anyway.
The real issue, like you mentioned, is the bandwidth/colo issue. Let me assure you, that I did not go and rent some colo space online and pop a desktop on a shelf on it's side. I have enterprise hardware buried away somewhere, and while you have shown how fragile the charade can be, I'm confident that with a combination of tunnels, I can truely hide the hardware by the time it becomes necessary.
Outside of that, I hope to be able to build a community that is strong enough to move past the concept of needing a centralized website if all else fails. I'm prepared to move off-internet if need be.
It's not necessarily an issue with your system. You seem to be more about articles and forum posts.
I've been toying with how to build an open source, decentralized replacement for social media and publishing platforms like YouTube, Patreon, etc.
The problem with crypto is normies are never going to deal with wallet keys and exchanges, especially with the way the SEC is trying to make sure they get their slice, and don't get me started on Libra.
From the little bit of the research I've done, to even build our own payment processor (not even the engineering side, I'd build it piece by piece if I had to) we'd need an undersigning bank.
Back to your project, if you would like me to run an a full audit (instead of the ten minutes I played around) and help you fix it, let me know. I've hardened WordPress blogs before, especially if you haven't moved to BitMitigate yet.
He's got a bit of a point, though. They don't need to take your server down if they can pressure your ISP - or your ISP's ISP - to pull the plug, or if they can close down however it's funded.
Okay, so you built the server and are colocating it somewhere? Do you own the connection and bandwidth yourself? There's a point of failure.
Then you might want to disable XML-RPC (or just pingbacks) in WordPress so that you stop leaking your hardware IP. I'd probably audit the other plugins and/or themes you're using (since you apparently "own" them, wtfever that means) so they don't leak as well. CloudFlare is nice, but it's not magic.
See the above.
lol it's not the DMCA that is going to deplatform you. It's going to be ISP related, or payment related. Ask NewProject2.
I've banned access to xmlrpc.php from the outside altogether. Can you verify?
You don't have to be a dick to make me hear you.
Verified.
Sorry, I see talk about this kind of thing all the time, but it's usually just smoke blown.
I'm more interested in figuring out how to properly address the payment issue, but if you want any engineering help, hit me up.
Explain a bit about the payment issue you forsee. I am self funding this and have the means to privately fund it for years to come without needing external income. Outside of that, BTC can be used for lightweight payment processor bypass, but it shouldn't be necessary anyway.
The real issue, like you mentioned, is the bandwidth/colo issue. Let me assure you, that I did not go and rent some colo space online and pop a desktop on a shelf on it's side. I have enterprise hardware buried away somewhere, and while you have shown how fragile the charade can be, I'm confident that with a combination of tunnels, I can truely hide the hardware by the time it becomes necessary.
Outside of that, I hope to be able to build a community that is strong enough to move past the concept of needing a centralized website if all else fails. I'm prepared to move off-internet if need be.
It's not necessarily an issue with your system. You seem to be more about articles and forum posts.
I've been toying with how to build an open source, decentralized replacement for social media and publishing platforms like YouTube, Patreon, etc.
The problem with crypto is normies are never going to deal with wallet keys and exchanges, especially with the way the SEC is trying to make sure they get their slice, and don't get me started on Libra.
From the little bit of the research I've done, to even build our own payment processor (not even the engineering side, I'd build it piece by piece if I had to) we'd need an undersigning bank.
Back to your project, if you would like me to run an a full audit (instead of the ten minutes I played around) and help you fix it, let me know. I've hardened WordPress blogs before, especially if you haven't moved to BitMitigate yet.
He's got a bit of a point, though. They don't need to take your server down if they can pressure your ISP - or your ISP's ISP - to pull the plug, or if they can close down however it's funded.
Check my replies above and feel free to add your take.