Microsoft is shit. Windows, is shit. Windows 11 is a privacy goddamn nightmare.

But in the end of the day, it just fucking works, those damn bastards ensure that. And even when something doesn't work, it seems, for some unknown reason, most of the online solutions do fix the issue.

Hahahahahahahahahahaha

(Pause for breath)

Hahahahahahahahahahaha

Only if you count "most of the online solutions" as "run SFC /SCANNOW and if that doesn't work, just reinstall your OS".

McAfee wrote a program that used the Sqlite library for database storage.

When going about its data storage business for McAfee's program, the Sqlite library was storing files in C:\temp with prefixes like sqlite_3726371.

Users see that and get angry, and bug the Sqlite developers.

Now probably when initialising the Sqlite library McAfee could have given it the location of a directory to keep it's temp files. Then they could have been tucked away somewhere along with the rest of the McAfee code base and be more easily recognised as belonging to them, but they didn't.

So because of a bit of careless programming on McAfee's part, Sqlite developers were getting the heat because the files were easily recognisable as belonging to them.

Because the Sqlite developers don't have control of what McAfee was doing, the most expedient way to solve the problem was to obfuscate the name a bit.

"I think there's something wrong with the door switch on my old microwave oven. I've been testing it outside for safety, that's why it's out in the back yard pointing upwards with the door open."

The filesystem driver knows the size of the filesystem is larger than the physical size of the partition it is on. Because of that it refuses to do anything with it until that discrepancy is sorted.

Boot to a USB/ISO, run cfdisk, extend the partition size back to original or larger, then run fsck on the partition again.

"Hello I'm dgriffith, a community support member here at (official support forum) and I'm here to help.

Have you tried formatting your hard drive and completely reinstalling your OS? That often helps when your icons are misaligned on the desktop.

If this post helps, please mark it as useful, thanks!"

It's a perfectly cromulent word that describes the process that happens across nearly all consumer corporate endeavours, online included.

Small ISPs at the start of the internet used to provide you with space that you could ftp a few html files to and they'd be visible on the internet at myisp/~yourusername.

Of course that cost them a little bit of money and storage space so when they all got absorbed into megaISPs that kind of thing got dropped. Then it was all up to Geocities and friends or you had to go buy hosting from your ISP, both of which was enough of a hurdle to stop the average person from playing with it.

A lot of the software components under the hood in Linux are replaceable.

So you have a bunch of different CPU and disk IO schedulers to suit different workloads, the networking stack and memory management can be tweaked to hell and back, etc etc.

Meanwhile Windows Server 2022 has...... ?

Ok I'll just inject a little bit of context into those numbers because it smells faintly of a hit piece by Reuters, simply because of the timeframe used and the number of employees spaceX has.

My experience is 30 years in the mining industry, which in that time has become pretty good at managing safety, and reporting on it.

So I'll dig in a little.

Since 2014, so nine years.

SpaceX employee count : 13000 approximately.

Take about a quarter of that to weed out the paper pushers and company growth since 2014, gives us 3500 or so employees in the line of fire (that is, manufacturing and such).

600 reportable injuries, so about 66 injuries a year. About 5.5 a month on average, over 9 years.

Now those 3500 employees work 60 hour weeks (because: spaceX). So 5.5 injuries and 840,000 man-hours a month. I'm going to round those hours up to 1 million for convenience and to counter the fact that I ditched quite a few people in my initial assessment of SpaceX employees in the line of fire before.

And with a bit of half-assery , I say, "ta-da!" and get 5.5 reportable injuries per million man-hours at SpaceX over the last 9 years.

So, what kind of number is that? Well for tracking this kind of thing normally you would work on a value called that "lost time injury frequency rate" - LTIFR - which is the number of injuries per million hours worked. Oh look, my previous rounding to a million has become very convenient.

Looking at the data that Reuters has given, and my half-assed guesses about employees, spaceX has a long term LTIFR of 5.5. Note that number drops significantly if you use SpaceX's entire employee base, which as a single entity, they would be quite entitled to use and report.

How does that number stand up against industry norms? 5.5 is middle of the road for manufacturing and construction, generally, but that includes all sorts of manufacturing, from building houses, to steel foundries , to making cars.

The fact that Reuters had to take 9 years of data to make the raw numbers sound alarming enough is a bad smell. They could have calculated LTIFR numbers for each year and figured out a trend and if that was alarming enough, they could have reported on it, like "SpaceX increasingly dangerous to work at!". The fact that they didn't makes me suspect it's a hit piece, although I am willing to accept they didn't want to get into LTIFR numbers and are dumbing it down for the general public.

Absolutely the number of serious injuries is a concern. Serious injuries are also at the top of a "injury pyramid", with every layer underneath broader, all the way down to "Ow, I stubbed my toe". If you have real figures for one layer (like a layer where an employee can't hide an injury), you can get a good idea of what the other layers should look like.

Judging from Reuters' numbers, the bottom "minor" layers aren't getting reported enough, which suggests a lack of safety culture at SpaceX. Although that could simply be from Reuters' using only public records, which, you know, only keep track of injuries worth keeping track of, so the bottom of that pyramid might only be seen by SpaceX internally.

In conclusion, the reporting by Reuters of raw numbers over long timeframes is suspect. That's not how things are done in the safety industry, which works with weighted metrics to get results they can compare between companies. Dig in a bit further yourself.

It brings that consistent Seattle blandness everywhere it goes.

Neal Stephenson said it best in Snow Crash :

"In olden times, you’d wander down to Mom’s Café for a bite to eat and a cup of joe, and you would feel right at home. It worked just fine if you never left your hometown. But if you went to the next town over, everyone would look up and stare at you when you came in the door, and the Blue Plate Special would be something you didn’t recognize. If you did enough traveling, you’d never feel at home anywhere.

But when a businessman from New Jersey goes to Dubuque, he knows he can walk into a McDonald’s and no one will stare at him. He can order without having to look at the menu, and the food will always taste the same. McDonald’s is Home, condensed into a three-ringed binder and xeroxed. “No surprises” is the motto of the franchise ghetto, its Good Housekeeping seal, subliminally blazoned on every sign and logo that make up the curves and grids of light that outline the Basin.

The people of America, who live in the world’s most surprising and terrible country, take comfort in that motto."

Article summary:

Linux: Do this.

Apple: Do this.

Windows: Conspicuously absent.

Config state is an absolute shitshow on windows. Is this application's config in $APPDATA/local? Roaming? The registry? Under HKEY_LOCAL_MACHINE? USERS? In its own folder in Program Files, oh Program Files(x86)? Maybe it's just in a folder in $USER.

Gives me the shits.

Article is good though, just wanted to vent.

Suitcase sized device? Only one or two of them nearby? Then that's not a problem.

If you scale it to industrial sizes/quantities then the extra salinity in the area where you dump the waste products becomes an issue.

Eg my coastal city uses about 135 megalitres of water a day. Supplying all that from seawater requires you to put about 5 metric tons of salt somewhere, every 24 hours.

Stick 5 tons of salt a day directly in one place in shallow waters just offshore and you'll end up with a dead zone a mile wide pretty quickly.

So now you've got to water that salt down into something that's only slightly saltier than usual and that can be difficult because for my example 135 million litres of water a day, you want to dilute the waste by at least 10x that (to make it approx 10 percent saltier) and now you're cycling a billion-plus litres a day around the place.

So this is pretty cool stuff, but just need to be careful with the side effects when it's scaled up.