You have it wrong, which really shows what you stand for:

Cloudflare refused to block KiwiFarms as there was no evidence of criminal activity or violation of their policies, and doing so would tarnish their reputation in regards to free speech. They did stop hosting KiwiFarms, in September of 2022 (you can find their statement here) in response to a libelous pressure campaign ran by Keffals when she/they/it found out users were pulling out receipts of it engaging in lewd conversation with minors and providing them with DIY hormone replacement therapy kits without any medical oversight or parental consent.

And KF did not attack Keffals out of nowhere, it was only after she started engaging with Chris-chan as she was attempting to use him to boost her own reputation at a time when he was already in a perilous mind.

I’m not sure exactly where you got the “threatening trans people” from, that is the first I’ve heard of it. I know of one incident that is much more grave and potentially what you are referring to, but your reference leaves out almost the entire context of that one particular incident and there have been no repeats of it to my knowledge.

I’m not a fan of KiwiFarms, but they did not earn their censorship. It was the result of a successful attempt by a revisionist career troll to cover their tracks when they realized their goose was about to get cooked, nothing more. If you truly stand for free speech, you would realize just how dangerous the precedent set by such an unreliable source as Keffals is.

And yes, I realize that if my comment gains enough traction, it and its army will be at my throat and by no doubt have doxxed me in no time if they so choose. But that’s not going to keep me from preventing people like you from twisting the narrative.

I just checked and they actually disabled AI Overview. LMAO

You’re remembering correctly, every other logic gate can be built from NAND gates, which is the foundation of this sort of minimal-instruction-set exercise. Beyond that, you need to be able to move data and change your program counter (jump, often conditionally). Then, if you want parity with modern instruction sets beyond just being turning complete, you need return and interrupt for control flow.

lol why?

Bookmarking your comment so I can come back to it in a couple hours, if I hopefully remember to.

But yes, almost. I don’t think the interrupt is necessary and the return isn’t under certain architectures. I have a doc on my computer somewhere where I was investigating what the absolute minimum was to make a turning complete machine and, to my recollection, there was only 4-6 instructions that were absolutely necessary. The ones I remember off the top of my head are NAND, MOV, JUMPIF, and then I believe I included NOP in accordance with some principle. RET and INT were convenience features in this design.

there is an additional layer to this joke for those who understand turing completeness. And it elevates it to a whole other level of snark.

Just give up hope. It’s really not worth it.

I loved Pop!_OS as it made Debian/Ubuntu extremely usable as a daily driver. Finally I got fed up with outdated package bullshit coming from different angles and went to Rocky. Wish I did it sooner.

Appreciate System76, but they’ve dropped the ball hard and I don’t think it’s recoverable

If I were to fully elaborate, I’d be typing for hours, so I’ll sum up:

• pip - default behavior is to install to system-wide site packages. In a venv, it will try to upgrade/uninstall system packages without notice/consent unless you specify --require-virtualenv. Multiple things can fuck up your ENV to make the python binaries point to system-wide, while your terminal will still show you as in a venv. Also why TF would package metadata files need to be executable? Bad practice, -1/10
• nix - they acknowledged years ago that they should probably have some kind of package signing and perhaps an SBOM or similar mechanism, but then did nothing to implement it and just said “oh well, guess we’re vulnerable to supply chain attacks, best not to think about it”
• brew - installing packages parallel to your system packages manager, without containers. My chief complaint here is that brew is a secondary package manager that people might treat as a “set and forget” for some packages, rarely updating them. So what happens when a standard library used by a brew package is vuln? A naive Linux user might update their system packages but totally forget to update brew. And when updating brew, you can easily hit max_open_file_descriptors because kitchen sink

From there, it’s all extremely nit-picky and paranoid-fueled-- basically, none of the package managers I mentioned are conducive, in my eyes at least, to a secure and intuitive compute environment.

Unfortunately, there’s not much I can do about it except bang pots and pans and throw maintainers under buses when the issue that has been present for years rears it’s ugly head. Because they are the only ones who can change this, and pressure is the only thing that might motivate them to.

Nix is already beyond fucked because they actively dismiss the need for appropriate security measures to prevent supply chain attacks. There were multiple discussions about this over the years that appear to have succumbed to neglect.

I wouldn’t trust nix, just like I don’t trust pip, brew, or a whole plethora of other package managers and repositories. They are just too neglectful