NaibofTabr

By the phone company.

Heh, that won’t stop a C-level from thinking that you just write code.

hmm…

hmm…

…and my axe!

It is an absolute PITA to keep an email server on the “nice” list so your company’s email traffic doesn’t get spam filtered by every service provider, and the major services (gmail, outlook, etc) are all federating their spam filter lists so many times if you get blocked on one you get blocked on all. There is so much spam to deal with that the filtering is highly automated and there’s little human oversight.

The point being, it could only take a handful of incidents reporting a company’s email as spam to ruin their reputation and result in email from their domain getting automatically filtered everywhere. So, you know, if they don’t support an easy way to unsubscribe then they are in fact behaving like spammers, so flag them and let them deal with having their domain blacklisted.

VPNs as a technology might not be illegal but circumventing the firewall certainly is.

Unless you are very vocal and high profile person no one will black bag you in a country of billion people, lol.

This is a bit of a misunderstanding about how things work in an authoritarian system. Sure, you might fly under the radar for awhile, but if you call attention to yourself (say, by getting caught trying to bypass the government firewall) and you are not high-profile, then it is very low-effort to make you disappear. Few will notice, and those that do will stay silent out of fear.

If you are more high-profile you still get black-bagged, you just get released after, with your behavior suitably modified.

Naomi Wu no longer uploads to YouTube.

Depends - how many family members do you have that the PRC might use against you? or who would miss you if the PRC black bagged you?

And there are hundreds if not thousands of them, plus a lot of automated tooling.

Amazon is a terribly exploitative company, but… they might actually be better than Oracle, and AFAIK Bezos isn’t in bed with Trump like Ellison is.

Beyond your eventual technical solution, keep this in mind: untested backups don’t exist.

I recommend reading some documentation about industry-leading solutions like Veeam… you won’t be able to reproduce all of the enterprise-level functionality, at least not without spending a lot of money, but you can try to reproduce the basic practices of good backup systems.

Whatever system you implement, draft a testing plan. A simpler backup solution that you can test and validate will be worth more than something complex and highly detailed.

I mean… exposed to each other, sure, but they’re all exposed to Syncthing and the public relays.

It is a fantastic idea to start your home server project on some e-waste hardware, and use it until you know specifically what features you’re lacking that you would need better hardware for.

Er, wait, are you using Syncthing for its intended purpose of syncing files across devices on your local network? And then exposing that infrastructure to the internet? Or are you isolating Syncthing instances?

Almost all of these turn into attempts to get the target to buy into some crypto scam or other.

It’s not meant to catch people who are moderately aware, it’s meant to catch the stupid, ignorant, and easy to manipulate. Being an obvious scam is part of the utility - it saves time by naturally filtering out anyone who is too aware to actually give them any money.

The issue is more that trying to upgrade everything at the same time is a recipe for disaster and a troubleshooting nightmare. Once you have a few interdependent services/VMs/containers/environments/hosts running, what you want to do is upgrade them separately, one at a time, then restart that service and anything that connects to it and make sure everything still works, then move on to updating the next thing.

If you do this shotgun approach for the sake of expediency, what happens is something halfway through the stack of upgrades breaks connectivity with something else, and then you have to go digging through the logs trying to figure out which piece needs a rollback.

Even more fun if two things in the same environment have conflicting dependencies, and one of them upgrades and installs its new dependency version and breaks whatever manual fix you did to get them to play nice together before, and good luck remembering what you did to fix it in that one environment six months ago.

It’s not FUD, it’s experience.

This is also a great way to just break everything you’ve set up.

Removed by mod

Really depends on where and how the data collection is integrated.

Browser forks mostly make changes to the application UI which wraps the engine, not to the engine itself. Browser engines are these fantastically complex things, extremely difficult to keep operational and secure, which is why there aren’t many of them and why they’re all developed by large organizations. Forking the engine is basically doomed to failure for a small project because you won’t be able to keep up, you’ll be out of date in a month and drastically insecure in a year.

This is basically all there is.

Removed by mod

Removed by mod