This is why companies have cheap toilet paper by the way. Not because they necessarily hate their employees, but because it would get stolen and they’d need three times as much.
Also one of the reasons why the huge rolls exist like you see at airports: impractical to use at home.
I read that stuff a few weeks ago. And the responses and discussion on Kagi’s Discord. I’ll continue to monitor Kagi’s behavior, of course, but for now I prefer Kagi. I get far more relevant results with no advertising noise and as much or as little “AI” assistance as I want.
Google is a cesspool and DDG is simply inferior - worthy, but inferior.
Try Kagi. Paid search engines are the future in order to extract yourself from the enshittification of “free” search engines.
I’ve played DSP, it’s a great game too. I’ll probably jump back to that when I burn out on Planet Crafter. The thing I don’t like about it and Satisfactory is conveyor belt management. The constant battle to rewire the spaghetti.
Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.
Boy, I doubt that.
My Windows 11 machine doesn’t require any of that.
I’ve been playing Planet Crafter waaay too much. Check it out if you like Factorio, Satisfactory, etc. It’s fun and super addictive. At least to me.
One day soon someone will search online for what to do for a cut and some AI will spit out “Blood letting can actually be healthy in many American males, since often they have a overabundance of iron…”
ChatGPT and github copilot are great tools, but they’re like a chainsaw: if you apply them incorrectly or become too casual and careless with them, they will kickback at you and fuck your day up.
Steam has to be worth a lot more than 12 billion.
Kagi is good. I’m using the unlimited search tier. It’s so nice not to have all the cruft in my searches.
You may know this, but the Nazis were forced into using hydrogen instead of helium because the only commercial sources at the time were in he USA and we wouldn’t sell it to them. But also, since the ship was built for German propaganda they would have wanted it to be a fully German endeavor.
The Hindenburg was painted with silvery powdered aluminium, to better show off the giant Nazi swastikas on the tail section. When it flew over cities, the on-board loudspeakers broadcast Nazi propaganda announcements, and the crew dropped thousands of small Nazi flags for the school children below. This is not surprising, because the Nazi Minister of Propaganda funded the Hindenburg.
At that time, the US government controlled the only significant supplies of helium (a non-flammable lifting gas), and refused to supply it to the Nazi government. So the Hindenburg had to use flammable hydrogen.
As the Hindenburg came in to Lakehurst on May 6, 1937, there was a storm brewing, and so there was much static electricity in the air - which charged up the aircraft. When the crew dropped the mooring ropes down to the ground, the static electricity was earthed, which set off sparks on the Hindenburg.
The Hindenburg was covered with cotton fabric, that had to be waterproof. So it had been swabbed with cellulose acetate (which happened to be very inflammable) that was then covered with aluminium powder (which is used as rocket fuel to propel the Space Shuttle into orbit). Indeed, the aluminium powder was in tiny flakes, which made them very susceptible to sparking. It was inevitable that a charged atmosphere would ignite the flammable skin.
In all of this, the hydrogen was innocent. In the terrible disaster, the Hindenburg burnt with a red flame. But hydrogen burns with an almost invisible bluish flame. In the Hindenburg disaster, as soon as the hydrogen bladders were opened by the flames, the hydrogen inside would have escaped up and away from the burning airship - and it would not have not contributed to the ensuing fire. The hydrogen was totally innocent. In fact, in 1935, a helium-filled airship with an acetate-aluminium skin burned near Point Sur in California with equal ferocity. The Hindenberg disaster was not caused by the hydrogen.
The lesson is obvious - the next time you build an airship, don’t paint the inflammable acetate skin with aluminium rocket fuel.
https://www.abc.net.au/science/articles/2004/02/26/1052864.htm
Thor at Pirate Software played it and really liked it, probably part of that.
Razer designing and selling a piece of medical equipment is an idea that should never have survived the brainstorming session.
I’ve had to have conversations with emoyees before about hygiene, slovenly appearance. One guy about his need to wear a belt because his ass-crack was constantly on display to the point people complained to HR.
It’s always awkward.
Having a language dependent on indentation is absurd on the face of it. It’s a ridiculous idea that should have been ridiculed from the outset.
I’m a Boomer myself (born in 1964) and this maybe the first legitimate occasion I’ve had to say “Okay, Boomer.”
Out of touch.
It’s aptly named then, “Crabtree Falls”.
Decent pun but I can’t say I’m lichen it.
Does he know about cashews?
The malicious code was written and debugged at their convenience and saved as an object module linker file that had been stripped of debugger symbols (this is one of its features that made Fruend suspicious enough to keep digging when he profiled his backdoored ssh looking for that 500ms delay: there were no symbols to attribute the cpu cycles to).
It was then further obfuscated by being chopped up and placed into a pure binary file that was ostensibly included in the tarballs for the xz library build process to use as a test case file during its build process. The file was supposedly an example of a bad compressed file.
This “test” file was placed in the .gitignore seen in the repo so the file’s abscense on github was explained. Being included as a binary test file only in the tarballs means that the malicious code isn’t on github in any form. Its nowhere to be seen until you get the tarball.
The build process then creates some highly obfuscated bash scripts on the fly during compilation that check for the existence of the files (since they won’t be there if you’re building from github). If they’re there, the scripts reassemble the object module, basically replacing the code that you would see in the repo.
Thats a simplified version of why there’s no code to see, and that’s just one aspect of this thing. It’s sneaky.
It’s okay to plagiarize books if they’re in a library.