this post was submitted on 30 Jul 2024
159 points (92.5% liked)

Selfhosted

40329 readers
492 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I saw this post today on Reddit and was curious to see if views are similar here as they are there.

  1. What are the best benefits of self-hosting?
  2. What do you wish you would have known as a beginner starting out?
  3. What resources do you know of to help a non-computer-scientist/engineer get started in self-hosting?
you are viewing a single comment's thread
view the rest of the comments
[–] EncryptKeeper@lemmy.world 1 points 3 months ago* (last edited 3 months ago) (1 children)

That only applies to posts on their forums. Not the content on your VPS

[–] mesamunefire@lemmy.world 0 points 3 months ago (1 children)
[–] EncryptKeeper@lemmy.world 1 points 3 months ago* (last edited 3 months ago) (1 children)

Incorrect. It applies only to the forums. It does not apply in any way, shape, or form to your VPS or the content on it. It’s one thing to be mistaken, but let’s not spread misinformation on purpose.

A Reddit post incorrectly took portions of our Terms of Service out of context, which only pertain to content provided to Vultr on our public mediums (community-related content on public forums, as an example) for purposes of rendering the needed services – e.g., publishing comments, posts, or ratings. This is separate from a user’s own, private content that is deployed on Vultr services.

Since our inception, Vultr has been committed to upholding and adhering to the strictest data privacy and protection standards across the world (including HIPAA, GDPR, and DPDPA). Our customers own 100% of their content.

[–] mesamunefire@lemmy.world 0 points 3 months ago (1 children)

It appears after the controversy they removed the parts https://arstechnica.com/tech-policy/2024/03/after-overreaching-tos-angers-users-cloud-provider-vultr-backs-off/

But when I read the tos, it was pretty clear it was not limited.

You also had to agree without an opt out which was scammy. There are better providers out there.

[–] EncryptKeeper@lemmy.world 0 points 3 months ago* (last edited 3 months ago) (1 children)

I don’t think you read the TOS. I think you read the out of context snippet and assumed that it applied to your VPS. They removed that bit because it was confusing, not because it was not limited.

Being forced to agree to a TOS change without an opt out is scummy, but that’s not limited to Vultr. Companies are not out there with multiple versions of TOS based on what people agree to or not. At that point you’re better off not using a VPS.

[–] mesamunefire@lemmy.world 0 points 3 months ago

Welp I'm an anonymous person on the Internet so you can believe what you want. I could say that my job is literally mass deploying servers (devops) but if you don't believe me that I said that I read it then I'm not sure what we can agree on.

Let's just stop while we are both ahead. It's a Thursday, good day for coffee yeah? Hope you have a good day.