188
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Mar 2024
188 points (87.9% liked)
Selfhosted
40383 readers
649 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Vultr posted their response to the concerns here - https://www.vultr.com/news/a-note-about-vultrs-terms-of-service/
The portion of the ToS that people were worried about had been in place for years and had nothing to do with server intellectual property. They are removing it to avoid future confusion.
I don't disagree that it was poorly worded, but the amount of people jumping to the worst possible conclusions on this is concerning. What happened to Hanlon's Razor?
Many are, but as far as I know, no hosting provider has ever tried something like what was claimed (which is why it made such news).
It seems like many people didn't even verify that portion of ToS was new (checking web archive), or wait for Vultr's response before closing their accounts.
Even after the official response, it feels like people stuck to their original assumptions and felt justified moving services?
Companies, and specifically the people in them, make mistakes. What matters is their reaction. I'm scratching my head to think what Vultr could do better in this case (other than creating a time machine to avoid the initial screw up).
_
What response are you expecting, exactly? There's lots of competition out there and data privacy is an extremely sensitive topic. It's not the kind of mistake you can recover from. They screwed up, they lost customers, end of story.
Also personally I don't believe for a second that it was a mistake. The hell it was. Any lawyer worth their salt would have pointed out the issue right away. Either they wrote it without a lawyer or they wrote it on purpose.
There was substantial room for improvement in the way they spoke publicly about this issue. See my comment above.
In the EU, it sort of isn't.
Takes a long time to write a proper response for all the GDPR stuff. The responses surprisingly don't change all that much whether or not I do, so I might as well save me the trouble.
I still don't like how flippant they've been in every public communication. I read the ToS. It's short for a ToS, everyone should read it. They claim it was taken "out of context," but there wasn't much context to take it out of. The ToS didn't make this distinction they're claiming, there was no separation of Vultr forum data from cloud service data. It was just a bad, poorly written ToS, plain and simple.
They haven't taken an ounce of responsibility for that, and have instead placed the blame on "a Reddit post" (when this was being discussed in way more detail on other tech forums, Vultr even chimed in on LowEndTalk).
As for this:
This means nothing. A simple "we are enhancing your user experience by mining your data and giving you a better quality service" would have covered them on this.
We only got an explanation behind the ToS ransom dialog after their CMO whined in a CRN article. That information should have been right in the dialog on the website.
In both places, they've actively done vague things to cause confusion, and are offended when people interpret it incorrectly.
If this is their attitude to a clear self-inflicted fuckup, then that’s plenty reason for me to avoid them and their services. It’s not like their services were distinct in any way… just a dime in a dozen cloud provider.
https://en.wikipedia.org/wiki/PRISM
https://en.wikipedia.org/wiki/Tempora
we're a little traumatised.
Very glad I took a step back and didn't make a knee jerk reaction to this. I'm responsible for recommending providers to clients and managing their k8s clusters. We use Linode, DigitalOcean and Vultr and had just set up a cluster on Vultr which would have been embarrassing to then have had to recommend moving. And the region we needed that cluster in the other providers don't cover. The response from Vultr has been good I think. And that goes with the level of support we've had from them which has been really good.
Rossman happened. He has videos that need watched.
Nothing. Apply Hanlon to the very original response to Vultr. It all works out.
It’s Hanlon all the way down.