What do you mean bring them back? They didn’t really go anywhere as a whole. There are still forums out there, it’s just far more popular to use Discord now. If there is a particular forum you have in mind, the way to bring that back is to host a replacement and then try to convince people to use it. It’s pretty trivial to set up some forums.

That’s not how certificates work. In fact, the whole point of certificates is so a man in the middle can’t do that.

When you try to visit a website at for example websiteA.com, your browser will look at the cert it receives for the website and make sure it was signed by a trusted CA, which your browser keeps a list of locally. A MiTM could make a fake CA to sign their fake websiteA.com certificate with, but your browser would obviously have no record of that fake CA and wouldn’t trust it.

In order for the attack you’re suggesting to work, the attacker would have to gain access to your host itself and plant their fake CA cert on your computer. Or somehow compromise a real trusted CA which would be… a pretty huge deal.

Or just roll your own recursive DNS server.

No the DC won’t have 1-2 techs per client, the clients themselves will have at least 1-2 techs or sysadmins or what have you to manage the hardware. And those guys will need to be somewhere in the general vicinity of the DC to go there if there’s a problem, physical inspections, etc.

It wouldn’t necessarily create jobs at the DC itself but in client companies utilizing it.

If it’s a colo data center I can see it bringing lots of local jobs. For each unique tenant in the building they’ll need at least 1-2 people within driving distance. But if it’s just like a big remotely managed AWS data center… not so much.

People here don’t dislike concept of AI, they dislike AI companies stealing data and shoving AI where it doesn’t belong. There’s nothing wrong with locally hosted basic facial recognition.

As you look through these recommendations, keep in mind that source code storage will become in-scope for PCI DSS certification in the very near future.

That’s not “Windows phone” that’s “Windows mobile”, the precursor to Windows Phone, which didn’t release until 2010.

Shifting to Windows Mobile now, in 2006, Windows Mobile 6 had only about 10% market share, behind both Palm OS and Symbian, the latter of which held a whopping 60%. I looked further back in time and I do see that Windows Mobile had a 34% market share in 2001, however it was again dwarfed by PalmOS. It’s also worth it to note that that 34% wasn’t comprised mainly of cellphones, but rather barcode scanning guns in warehouses and logistics, because you could make custom applications for them with relative ease. There are still warehouses today that use those old windows mobile scanner guns.

Never at any point in time did the Windows phone reach 34% market share or anywhere near #1. I’m not even sure Windows phone had a bigger share than BlackBerry at the time.

Their peak market share was 3.4%, not 34%. It failed because virtually nobody bought them.

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.

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.

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

I’ve been eyeing that up since I’m a business management game kinda guy. But it depends on exactly how jank it is. Is it worth playing?

EDIT: As I suspected, the changes that u/mesamunefire is referencing are the ones that taken out of context awhile back and incorrectly assumed to apply to user VPS’ and the data on them, which is not the case. Those terms only apply to information posted publicly to their website, like the community forums.

What changes would those be

To piggy back on your “You don’t need k8s or high availability”,

If you want to optimize your setup in a way that’s actually beneficial on the small, self hosted scale, then what you should aim for is reproducibility. Docker compose, Ansible, NixOS, whatever your pleasure. The ability to quickly take your entire environment from one box and move it to another, either because you’re switching cloud providers or got a nicer hardware box from a garage sale.

When Linode was acquired by Akamai and subsequently renamed, I moved all my cloud containers to Vultr by rsyncing the folder structure to the new VM over SSH, then running the compose file on the new server. The entire migration short of changing DNS records took like 5 minutes of hands-on time.

Caddy is so simple you don’t really need configuration examples. The extra configuration many docker services have you configure in Nginx are already done by default with Caddy. Though I have seen Caddy config examples around sometimes.

If all you’re using it for is reverse proxying, you don’t need config examples for Nginx or Caddy, just understand how to configure them.

That is the way it’s pronounced, yes.

What’s wrong with the search?

Also, sync contacts to what?

No, the LLM. The LLM is for use in ProtonMail only.

Like this collaborative document editor they added a month ago?

https://proton.me/blog/docs-proton-drive