BREAKING: The Epstein survivors are releasing this ad on Super Bowl Sunday to send the message that they WON'T “move on” from the largest sex trafficking scandal in the world.

They're asking people to "Stand With Us and Tell Attorney General #PamBondi It's Time for the Truth"

They direct people to the site worldwithoutexploitation.org
#standwithsurvivors #Epstein #SuperBowl
Edited update to add subtitles.
Edited to use the https link if you don't want to retype
https://www.worldwithoutexploitation.org/

In the middle of an international crisis over #Greenland, #Starmer has quietly without fanfare released the Joint Intelligence Committee / Defra report on
'GLOBAL BIODIVERSITY LOSS, ECOSYSTEM COLLAPSE AND NATIONAL SECURITY' that his government suppressed last October.

Don’t let it be buried. Please share!

‘Ecosystem degradation is occurring across all regions. Every critical ecosystem is on a pathway to collapse.’

#biodiversity
#ecosystem
#nationalsecurity

https://assets.publishing.service.gov.uk/media/696e0eae719d837d69afc7de/National_security_assessment_-_global_biodiversity_loss__ecosystem_collapse_and_national_security.pdf

An open-source AI agent running on my Mac mini server is the most fun and productive experience I've had with AI in a while.

Clawdbot by @steipete is a personal AI assistant that you can infinitely tweak. It runs in any messaging app (!), has access to skills, can use the shell, and – notably – it can improve itself because it's completely open to customization.

My story:

Clawdbot Showed Me What the Future of Personal AI Assistants Looks Like https://www.macstories.net/stories/clawdbot-showed-me-what-the-future-of-personal-ai-assistants-looks-like/

I've seen a number of people (including some well-respected people in the infosec sphere) promoting a particular blog post/writeup recently about the macOS secure boot chain. As someone who has done a fair bit of research and reverse engineering of iBoot and Apple's secure boot chain over the years, this naturally piqued my interest so I decided to take a look, at minimum to see how much it lined up with my RE of iBoot over the years.

Unfortunately after reading the blog post thoroughly, I can pretty confidently say this: the writeup is almost certainly a pile of AI slop. Let's dive into it and discover some major red flags that I found.

Let's talk about something that I think a lot of the people reposting this post haven't realized yet: this post was very factually wrong when it was first posted. (Here is a link to the earliest version on the Wayback Machine, very good resource btw ) Shoutouts to @nicolas17 btw for making archives once he noticed the article rapidly changing, he puts in a lot of work in the archival side of things that imo goes very unnoticed, but his work helps Apple security research in the long run.

This original version of the post has several factual errors (there are too many to list but some of the VERY obvious ones include Apple silicon chips starting at EL3 when no M-series Mac chip has implemented EL3 (which is optional per ARM spec) In addition there is contradictory info about the ECID, incorrect info on security fuses, etc, there's a LOT of slop to digest here along with tons and tons of jargon that makes no sense.)

The fact the post gets stuff wrong in and of itself is not the issue (a mistake here and there is completely understandable and in fact quite human), the issue is with the magnitude of how many factual errors were posted publicly, seemingly without any fact checking or sourcing, it really is quite egregious just how wrong this post is (even the current version of the post still has many of these errors), especially to any person who has even took a cursory glance at iBoot or the secure boot chain.

The syntax, per people I discussed this with, screams that it was based on prompting Claude (an LLM that seems to have more natural writing style than some of the others.)

However, what really is super insidious is the history behind this post. This is a link to diffs of the post over time, and it's pretty damning. The post had very very large chunks changed in very short amounts of time across multiple parts of the very long post, and with how long the post is, this is probably outright infeasible for a human to do in that short time frame (especially when incorporating time to fact-check the updated parts, which any writeup worth their salt imo should be doing.)

Per these two comments on HackerNews, along with the drastic changes mentioned before (especially considering that the post changed quite drastically between revisions, saved versions of which you can find here), it's pretty clear that what's been happening here is the person used AI to churn out this "writeup", then used the fact it was blatantly wrong to get people who knew how these systems actually worked to correct the post, and then told the AI to incorporate said corrections into the original post.

Let's be clear what's happening: the person is outright baiting people using this AI slop into correcting the post, incorporating said corrections without attribution to the people who corrected the post and then took the credit for said corrections silently. This isn't okay, this is a blatant abuse of community goodwill and the benefit of the doubt to fraudulently boost your own credibility and platform, without even a legitimate effort or attempt at doing proper research or fact-checking. (Not even diving into how LLMs are plagiarism laundering machines that yoink real human work and mash it together without any attribution.)

This "writeup" is nothing but of AI slop, and I strongly advise avoiding giving it attention. I'm very disappointed that people, even people I respect quite a bit, are promoting this like it's legitimate without reading it deeper and realizing this is AI slop.

Here are some writeups I strongly recommend reading, that have real, human, legitimate research placed into them:

• This fantastic writeup/thesis by Mortiz Steffin and Dr. Jiska Classen on the GXF-protected portions of iOS (SPTM, TXM, Exclaves/SecureKernel) and how it all makes XNU closer to a true microkernel architecture.
• JJTech's writeup on iMessage and how it worked as of 2023 (yes, 2023 was two years ago, but this writeup is still worth reading regardless)
• Snoolie's writeup on an Apple Archive vulnerability, this is a great writeup that goes further in depth on CVE-2024-27876.

obvious take, why didn't I think of this 😂

(source unknown, let me know if you know :)