recursive_recursion
/
p.d-blog
forked from Programming.Dev/p.d-blog
1
0
Fork 0
Code Pull Requests Activity

Update content/posts/Vultr.md 

Revisions made to:
- headers
- added Vultr's TOS
- removed extra lines
This commit is contained in:
recursive_recursion 2024-03-28 00:42:35 +00:00
parent da2a28a850
commit 7fca5c15d3
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/posts/Vultr.md
View File

@ -6,27 +6,29 @@ categories:
- Programming.Dev
- Bytes
- Forge
tags:
- Server
---
TL;DR:
Looking to migrate cloud service providers cause Vultr's looking to havest everyone's data >:P
## Vultr
## Vultr (Current Cloud Provider)
For clarification their [Terms Of Service](https://www.vultr.com/legal/tos/) last modified date states: "January 8, 2024";
- it's assumed that the date has yet to be updated.
<br/>
Vultr's new TOS (starting at [Section 12](https://www.vultr.com/legal/tos/#tos_12)) contains clauses that claims ownership of ALL user hosted content under a commercial "non-exclusive, perpetual, irrevocable, royalty-free, fully paid-up, worldwide license"...etc.
Vultr's new TOS (starting at [Section 12](https://www.vultr.com/legal/tos/#tos_12)) contains quite an amount of egregious overreaching clauses:
```
You hereby grant to Vultr a non-exclusive, perpetual, irrevocable, royalty-free, fully paid-up, worldwide license (including the right to sublicense through multiple tiers) to use, reproduce, process, adapt, publicly perform, publicly display, modify, prepare derivative works, publish, transmit and distribute each of your User Content, or any portion thereof, in any form, medium or distribution method now known or hereafter existing, known or developed, and otherwise use and commercialize the User Content in any way that Vultr deems appropriate, without any further consent, notice and/or compensation to you or to any third parties, for purposes of providing the Services to you.
```
- which is pretty ridiculous.
Based on the current state of the world, we're gonna assume this is for AI.
Either way even if it's not, we're jumping ship.
## Programming.Dev
## Cloud Migration Plans
Based on internal discussion we're currently looking into migrating to either Hetzner or Scaleway.
- we'll provide confirmation on which one we've chosen and when we'll migrate once we've figured out the pros and cons of either.