roooot retweeted
kinda crazy that we’re here now, but it’s finally time to say goodbye. it’s bittersweet, as i enjoyed all the chaos and new friends i made, but i’m excited for what’s ahead. thanks for all the support! ❤️
8
5
103
7,361
roooot retweeted
Cyanide 1.11.0 is out!
New Lara section: Performance HUD, Debug Overlay, hidden settings, JIT, 3-app limit fix & App Decrypt, rebuilt on Cyanide's own kernel access.
Huge thanks to @rooootdev for permission to port lara's features!
github.com/kolbicz/Cyanide/r…
6
15
72
6,814
roooot retweeted
With all of this in mind, I think it’s best that we don’t go out flaming people for their creations. If you don’t like something that’s vibecoded, it’s best to just ignore it, and if you’re a developer, you should use it as motivation to create and inspire human-made projects.
1
1
34
2,150
If I could have published it, I would have. Believe me. This bug was serverside though. Releasing it would have meant it being patched instantly for everyone everywhere forever.
2
17
716
The bug is patched for everyone dude. It doesn’t work anymore. What about this is so hard for everyone to understand?
1
20
1,442
2/2
this whole situation was already handled bad enough, from it spreading to WAY too many people like wildfire, to people accidentally publishing it on GitHub.
1
2
78
11,686
1/2
apparently the epic 0day cryptex haxx were patched. bummer. i ask that everyone involved NOT publish any proof of concepts or writeups, as im not sure if some workaround that could make it work again exists. (would be a shame to burn the bug twice)
12
8
210
20,863
As others noted, Apple patched the not-so-secret server side bug. It enabled root access and jailbreaking even on iOS 27.2b3 (18 Pro Max). A public release would've meant an instant patch, so it stayed private. Despite efforts to preserve it, it's cooked. RIP 🪦😭
60
107
1,308
323,786
