I’ve been coming to @defcon for almost a solid decade now. This was an awesome weekend!
Panel Talk @AppSec_Village ✅
Secure By Design Red Pen Session @DEFCONPolicy@CISAgov ✅
Winning @ThreatModelUs Contest ✅
And…seeing so many of my friends ❤️
Time to sleep 😴
And Compiler has been defeated less than an hour later on my first attempt.
What a journey and fitting end to Season 1. Absolute masterpiece of a game @MarathonTheGame
Today, we remember a legend.
On this day in history, Harambe would have celebrated another birthday. An icon that became part of internet history, American culture, and an entire generation’s timeline.
Tomorrow marks 10 years since we lost him. Ten years since the moment the world stopped scrolling and collectively mourned something bigger than a meme.
He became a symbol of loyalty, strength, chaos, unity, and the strange beauty of the internet bringing millions of people together for one cause: never forgetting Harambe.
Everyone remembers where they were when they heard the news. And somehow, a decade later, his legacy still lives on.
Gone, but never forgotten.
Rest easy to a true patriot. 🕊️🇺🇸
May 27, 1999 — May 28, 2016
Forever in our hearts.
What’s worse than going into ranked Cryo kitted with golds in Bronze and being matched with teammates with a blue and white shields.
Seriously? That’s the best you can match me with?
Over the weekend, a player posted a video of them taking advantage of a map issue and going out of bounds to gain access into the Compiler room to ambush a team after they finished completing the encounter.
First off, we will have this issue fixed before Cryo Archive becomes available again.
In the past, we have not taken action against players going out of bounds, but due to this case heavily affecting other players negatively, we'll be reviewing our policies and sharing more details soon. While we don't want to punish players for bugs that they run into by accident, we will communicate more clearly the line that players should not cross when it comes to using these sorts of bugs that could be griefing others.
We will be reaching out to the affected players to grant them compensation for having their successful run interrupted by this issue.
We were made aware of concerns regarding the visibility of chat messages and code on Lovable projects with public visibility settings.
To be clear: We did not suffer a data breach.
Our documentation of what “public” implies was unclear, and that’s a failure on us.
Specifically for public projects, chat messages used to be visible — this is now no longer possible.
When it comes to code of public projects: That is intentional behavior. We have experimented with different UX for how the build history is surfaced on public projects, but the core behavior has been consistent and by design.
Importantly, for enterprise customers, being able to set visibility to public for new projects has been disabled since May 25, 2025.
You’ve got Anthropic fear mongering everywhere about Mythos being too powerful at the same time as major organizations faking SOC2s, giving full scope access to OAuth tokens, and not doing AuthZ.
You’ve got Anthropic fear mongering everywhere about Mythos being too powerful at the same time as major organizations faking SOC2s, giving full scope access to OAuth tokens, and not doing AuthZ.