New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Yep. Lots of people like throwing around these accusations thinking that no one will question them. As Crunchbits said:
My guess is all the "evidence" in the accusation against alexhost is equally shallow (e.g. their lack of action being taken when a unverifiable report is sent their way).
Or, it could be this
Bonus
If VDS will meet your requirements, we use GSL full-time on and can even set custom filters on your specific IPs for our NL location. All EPYC servers, each server with > 1TB host-node RAM capacity, NVME Gen4, multiple links for redundancy, etc. Another option, others probably haven't mentioned, is having a protected IP on something like us from GSL or any other provider here with VDS or VPS and using a tunnel (gre) to forward it to your backend server for protection of that server if they're physically close. That's actually an extremely common setup for what you need.
There's also some providers who specialize in something known as "GRE remote protection" - they give you a GRE tunnel with dedicated public IPs on it, you use those to mount your web servers to, and they give you a panel to control the DDoS protection on those IPs. This is what I recommend for your use-case actually - 100%.
Basic commands for example to setup something like that would be (in this example 1.2.3.4/31 is the GRE IPs, 4.3.2.2/24 is your dedicated server IPs):
Also can add that in /etc/network/interfaces for example as post-up commands under the GRE tunnel config. For extra security of the SSH service, you can even have it "listen" only on the original dedicated server IP and not the protected one, etc - to keep it from being targeted and only have your web services listen on that new IP.
you dont have ayes?
it takes months before police takes the case. The damage is children is already done by then.
this is completely different to copyright infringement you are doing. Highly illegal by law and simply not right
You still need to give them valid proof/evidence. A good host will not act on "trust me bro".
Point to an obviously illegal file hosted on an IP under their control and I'm sure they'll take it down.
The existence of the material require children to be harmed first. It's antecedent not succedent. Responsibility over prolonged harm to children in captivity lies on the police and law enforcement, whom bestowed by law, the ability to investigate and catch these abusers.
As said by the other person. Could you prove beyond reasonable doubt @alexhost unnecessarily delay the takedown process for CSAM content or ignored it?
yes, absolutely.
you need to question everything and you can't blindly trust others.
When you get an unverifiable report, what are you going to do? just blindly shut them down? bad actors use these tactics all the time. like crunchbits said they would just become an L7 DDoS service.
any privacy respecting service is bound to attract bad actors, does that still mean you don't verify blind, unverifiable claims? especially in the age where the primary tactic against people who promote privacy and government opposition is to plant CSAM?
You cant compare virtualized with bare metal performance lol?
Yes and no,
It's all depending on the underlying hardware, rather than the name on its own.
Well, I don't really give a fuck about AlexHost. I can't stop them anyway, but I won't ever give them even $1.
There are a lot of reviews on Trustpilot confirming this claim. Their reputation on other forums says the same, and I already talked to people who seem to have direct contact with them, saying: "I never had a problem with the Alex guy."
So I'm 100% sure they did something in the past. I don't know if they still support CSAM.
They also request court orders for reports like these, as you can see from many reviews on Trustpilot and other reputation forums.
https://www.trustpilot.com/reviews/6527cbf98aad0b8e15882e16
Here's an example story. I don't think everyone is making these stories up. If they were, other hosting providers would experience the same thing.
Ah right, so it's "if other people are saying it on the internet, it's gotta be true! Trust me bro!".
You really should be careful with such defamatory statements.
Which is legitimate. Many hosts don't want to look at the stuff themselves and will require either a lawful order or reporting by a trusted agency. In addition, in many cases they don't even have access to the material, e.g. if it's encrypted. In that case, they'd need either the password or a court order, otherwise they're just taking a claim at face value.
Of course you can, if there are no noisy neighbors (even better if you have one of those neat EPYCs that has a separate L3 for each core). And with VirtIO (or better yet, PCI passthrough e.g. SR-IOV rather than virtio-net), performance will be so close to native that you won't be able to tell the difference. The key is that you want a VDS rather than a VPS.
Responding after 6 days is still considered normal. He described his wife adolescent/teenage nude photos when she was 10-13 YO and dating got posted. There's no indication that she was groomed or trafficked. So, girl during puberty doing stupid shit with presumably her ex childhood boyfriend.
This was 3 years ago, not yesterday. And you're unable to supply any kind of proof that indicate @alexhost involvement/indicted by the authority for the specific claim you are making.
Yup, I agree
https://nodequality.com/r/UmfQUrTaXodmdZv32TvdiB8MjsRXaATE
This is a benchmark someone took of our enterprise VDS platform.
If you don't need much storage and just want raw compute and ram this is the best option.