Don't suck a billionaire's dick and tell me it's a lollipop.

I explained what I was thinking in the prior comment.

So it sounds like you know specifically how they identified the user's CPU. What means was actually employed?

It's all been over since we got processors with microcode, which could have something like a TPM in them. I'm not saying all of them do or anything like that, only that any of them could.

If you really want a computer you can trust, you're going to have to get vintage about it.

I hereby retract everything I just said. The entire post was based on a misunderstanding caused by Slashdot's editors adding a single extra letter.

• Original: "very explicit user action."
• Slashdot: "every explicit user action."

What a difference an 'e' makes. I was imagining every single file access causing a UAC dialog.

Yikes.

Well, no, I don't retract the last paragraph. They should still kick Meta's garbage agent off the platform until Meta can get security right.

The word was *every*. *Every* explicit user action.

Oh, bloody hell. I just got rage-baited by incompetent Slashdot editors.

Good night. I'm done for the day.

If this happens, this thirty-year Mac user will be leaving the platform. Full stop. So will just about everyone else within months to single-digit years.

This approach didn't work with Gatekeeper in Mac OS 7. It didn't work for Windows XP. It won't work for modern Mac OS, either. Here's why: CONSTANT PROMPTING MAKES SECURITY WORSE.

Prompting users over and over again to allow or deny actions makes security WORSE. Period. It means that users are constantly being nagged, and constantly having to decide whether an action is harmful or not. This rapidly (over the course of just minutes) turns into query burnout, and the user just clicks "Allow" for everything. And not only does it fail to meet its objective, but it also causes them to the same for every other dialog, including all of the other things Apple put in place to improve privacy and security. And now people are granting every app whatever access it asks for automatically without question, and every advantage that Apple has security-wise and privacy-wise evaporates instantaneously.

Continuous prompting NEVER makes security better. It ONLY makes security worse.

AND this would have a hopelessly deleterious effect on EVERYTHING that high-end users do, from running commands in Terminal (which would become completely unusable) to third-party backups, etc.

And that latter one would also be a major antitrust problem for Apple, which is to say that if they do this, they WILL get sued, and they WILL lose, because it is so clearly open-and-shut that this is not the correct solution for the problem, but that Apple stands to greatly benefit while their competitors are irreparably harmed.

What's described here would completely break the platform at a level that makes it a toy, no more useful than iOS, and completely unreasonable to use for any serious professional work, whether as a software engineer or a graphic designer. And it is pathetically absurd that they think this is a good idea. It makes me assume that none of the Apple security engineers I know are still around, because all of them would have flat out called you a moron for even suggesting something like this. They actually understood security at a more-than-superficial level. Someone proposing this "solution" clearly does not.

You can't fix sh**ty apps by making the platform objectively worse or making things that people legitimately need to do as painful as possible. The only way to fix sh**ty apps is by banning them from the App Store and flagging direct downloads as malware repeatedly until such time as they get their security model right. There are correct ways to sandbox things like agentic frameworks. This is about as far from the right way as you can get, as it does nothing to improve the security of the agentic setup, while catastrophically breaking overall platform usability and turning users into mindless "Allow" clickers.

Find another way. Kick Meta's horrific agentic tool off the platform until they can get security right.

Censorship means suppression of speech or expression by a governing authority. It can be prior restraint (blocking publication) or censorship after the fact (take-downs, bans, etc.).

In the strictest sense, you could maybe argue that soft moderation in the Slashdot style where people who want to see what has been moderated down doesn't qualify as censorship because there's a way around it, but the net impact is still that most of the potential audience doesn't see it, so that argument is on somewhat shaky ground.

At best, you can argue that moderation is not prior restraint censorship, but while prior restraint makes censorship way more likely to be a first amendment issue if the government is involved, it's not a requirement for something being censorship.

What do AI companies have to do with anything? The prompts would be generated by the company running the site, not the AI company. The quality of performance depends on the quality of the prompt and what data it has access to far more than on the model training.

No. Larry Ellison is a well known piece of shit. If you support him then fuck you too,b because you're also a piece of shit, just like everyone who voted for the orange child rapist.

IME it mostly works now. It's always slow and stupid and the UI is crap, but most of the features work most of the time

No, most people do not have a motherboard TPM, it's in the CPU.

Riot isn't identifying a Ryzen by staring at TCP packets. Vanguard runs on the PC, where it can collect hardware information or request TPM attestation and send the result to Riot. CPUID identifies a processor model, not an individual chip; a CPU-bound firmware TPM is a more plausible explanation for a ban following a used CPU.

TPM wouldn't work because you'd have to transplant it from one motherboard to another. The CPUID instruction gives a lot of information (including serial number) if you ask it the right way. It's how the CPU-Z application gets all that information - there's tons of information available via CPUID on a modern processor depending on what you load EAX/EBX can call it.

You slow the initial spread of posts for long enough to throw AI at the problem and analyze the factual accuracy of every post, or at least every post that any user flags as misinformation or factually incorrect.

For posts that are obvious satire (e.g. from known satire sites, etc.), flag them with a clear "This post is satire" warning at the beginning of the post.

For posts that are just flat-out lies, mass cancel the post automatically:

1. Prevent it from appearing in anyone else's feed or spreading.
2. Fan out the ban scan to recognize similar posts from people who saw the original post, recursively cancel those.
3. Backtrack to see if any posts that the original poster might have seen posted similar information from which the false post was derived, and recursively cancel those, including fan-out and backtracking from there, etc. until you have a complete graph of every post that appears to be derived from the lie.
4. Bulk distribute a post to everyone who saw the original post, explaining what was untruthful and why the bot believes that it was untruthful, providing factual citations to refute the original post. You do this in bulk to everyone who saw the original post all at once, not through organic spread, making it faster to refute a lie than to spread it originally.

In your fact checking ban post, you make it possible for anyone who believes that the cancellation was unjustified to submit external citations as evidence of its accuracy. After 72 hours, all citations submitted by anyone who saw the fact checking ban post are deduplicated, consolidated, and sent to a hundred human reviewers. These reviewers vote to either: A. reinstate the original post, B. reinstate the original post with clarification at the beginning (this post is mostly correct except XXX, this post is satire and is not intended to be taken as truth, this post is an opinion piece that disagrees with broadly held scientific consensus and the evidence presented herein should be treated with skepticism unless proven correct by larger/stronger/more robust studies, etc.), or C. uphold the ban.

If a post is reinstated, every post flagged as a consequence of the original flagging is also reinstated in a similar fashion, with clarification if applicable.

In other words, make it easy for users to report that something is a lie, make the resulting fact checking be aggressive at immediately halting the spread of things that are clearly untruthful, and make corrections spread faster than the lies did originally.

The last critical piece is the ability for an individual user to choose whether to see posts that have been flagged as being lies. If they choose to repost something that is already flagged, it will be seen only by other people who have chosen to opt out of hiding factually erroneous posts, so the spread will be mostly limited to those who have already bought into one or more conspiracy theories, but that's still moderation rather than outright banning of the content. And people would be free to write new posts that point out that a post on a subject has been banned and telling people why they think it should not be banned. Of course, in most cases, that will paint the person as a nutter, but at least you'll know. :-)

Unfortunately, at some point, in the U.S., certain political groups decided that things that are contrary to established facts are "opinions" that cannot be questioned, rather than lies, so demanding factual accuracy will be seen by many as political bias, which is why this will probably never happen.

Spying is a primary use of AI and it makes spying on more people more feasible.

It's the rapeublicans who are raping children. Literally marrying children so they can rape them.