The best case would be to protect everyone’s privacy, not just the children OR teens
The difference is that an adult can consent to having their data collected by these companies, making the investigation and enforcement a more nuanced endeavor. A child cannot, so it all becomes far more straight forward and easier to go after the offending companies.
There’s nothing magical about the 15th reboot - Crowdstrike runs an update check during the boot process, and depending on your setup and network speeds, it can often take multiple reboots for that update to get picked up and applied. If it fails to apply the update before the boot cycle hits the point that crashes, you just have to try again.
One thing that can help, if anyone reads this and is having this problem, is to hard wire the machine to the network. Wifi is enabled later in the startup sequence which leaves little (or no) time for the update to get picked up an applied before the boot crashes. The wired network stack starts up much earlier in the cycle and will maximize the odds of the fix getting applied in time.
I had to dig up some other sources for info, but this is the case. The new plant has nothing to do with coal, but it is being built to replace the power production and local power related jobs in that area.
Sources:
The article is critical of GitLabs model, not celebrating it.
What GitLab does is far more open than what you’ll see elsewhere, but the formula is actually pretty near to what most companies do already: Have pay bands for positions, and then a modifier based on the region, level factors, and some other inputs. Normally this produces a range, not a straight number, and then negotiations take place within that band (which is also why this information and formula is not typically shared).
As for the idea of paying a flat salary for a position regardless of where the person works, that is simply a non-starter for most companies, and essentially creates a race to the bottom to locate the region of the world that will produce qualified workers for the lowest possible salary possible. We as a society have no problem seeing fast fashion or other manufacturing that do this as being exploitive and evil, and this model is exactly the kind of thinking that drives that behavior. If we stop caring about where a person lives and instead look only at salary vs production, we will only ever hire in the absolute lowest cost of living places in the world capable of producing acceptable workers.
We need to look at this from another angle as well - Companies are buying labor, much in the same way that they buy raw materials, property, or utilities. When buying any of these inputs to your business, how do you decide how much to pay? Certainly you do not sit down in a board room and agree on a number and then go out into the world with that number and attempt to purchase what you need. You start by looking at what the going market rate for those inputs are. People, like materials, have some wiggle room in those numbers, and sometimes paying a little more will get you better quality or more reliability, so you will need to make decisions there to determine where on the spectrum you wish to fall, but never would you pay significantly more than market rate, nor would you be able to pay significantly below.
I see this kind of discussion constantly in the last few years, and often in terms of tying inflation to annual salary increases. “If inflation was 10%, why is my annual raise only 5%?” - because overall inflation was 10%, but the inflation in the cost for a person that can do your job was only 5%. It’s truly and honestly that simple. You are a commodity item that goes to the highest bidder - act like it.
It’s just a PC with a touchscreen that comes with Windows installed from the store. The only thing to really worry about are the hardware drivers for the unique bits.
Getting people sorted into servers that are going to be able to handle the load, or even better getting them to host their own servers is going to be the way to go.
That part still worries me a smidge, and it’s somewhat related to my other concern about funding/scaling. As more of the general public discover and move over, the % of the general population willing and able to host their own instance is going to steadily decrease. Not saying that we’re all gonna die or anything, but it’s going to be a shift and we’ll have to continue to adapt.
That feeling makes sense, but I think everyone knows that the Fediverse wasn’t created specifically to give them a landing in this event, just like Reddit wasn’t created to catch the Digg refugees, etc. More of a “next phase in the evolution of this concept”, and while it took a catastrophe, they’re ready to consider that it’s time to move on now.
The trick is going to be walking that line between preserving what made the Fediverse great and not alienating the newcomers. I think there’s room for everyone, though, and really the big advantage of the Fediverse - we don’t have to agree to co-exist, and can even co-existing completely separately if needed.
NSFW subs are exactly where my mind went as well, but monetizing some of that content could prove legally fraught. Instead, I’d wager the scope narrows a bit to a very specific OnlyFans type of model. Weren’t they already looking at paid awards that provide a cash reward to the recipient? Sure sounds like a tipping model to me 🤔