{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibmgaxz2r46cohu7znascixkofscxhe45pvnkwfbaflxa54bt4v24",
    "uri": "at://did:plc:ayfizlbmvprdzzpxhepnqrns/app.bsky.feed.post/3mm7yrpmjk5d2"
  },
  "path": "/f/technology/14947",
  "publishedAt": "2026-05-19T17:58:44.000Z",
  "site": "https://jstpst.net",
  "textContent": "Getting on the internet means having a server with an IP somewhere, and usually that means having a virtual machine on someones server. This is a VPS.\n\nSometimes this has problems and concerns (if the hosts security is bad, someone else on a different VPS but the same physical server might get your details. In practice, the concern is they can hoard the resources for themselves; this is called \"steal\" in process managers.)\n\nI was on Linode for awhile since it was a well-reputed VPS host but when they got bought by Akamai, I decided to leave for Digital Ocean.\n\nDigitalOcean has increasingly pivoted to \"AI\" stuff, and has recently revamped their entire website as \"AI Native Cloud\". They even fucked up their entire web console, replacing useful entries such as \"Droplets\" (servers), \"Volumes\", \"Databases\", \"Networking\", etc. to re-emphasize AI shit, primarily \"Inference\". It takes more clicks to do less now. All while its cloud services like Functions ('serverless' features) languish. (They still don't support Rust functions\n\nDigitalOcean is not bad enough that I need to move _now_ , but it's bad enough that when it comes time to try to update my LTS servers to a new distro, I'll probably just migrate my personal servers to a new one on a new VPS.\n\nI'm looking at Vultr- ah wait no, they're an \"AI first\" platform. OVHcloud, Hetzner, maybe even back to Linode.\n\nWah",
  "title": "Linode went Akamai and DigitalOcean is going AI :\\",
  "updatedAt": "2026-05-19T17:58:44.000Z"
}