mlx

[turbomander @turbomander]

god dammit my journey of self discovery just ended with me realizing what a huge piece of shit i am

[Zach @jestermaxxing]

Imagine if instead of glory holes we had ‘story holes’. Holes you can put your ear to and hear a wonderful story.

[ang @fatmustyincel]

You are not a sensitive lover boy You are a faggot

[mlx @mkiscg]

@oroseeeeee mon frr merci pour tout

[tendollar @tendollardanny]

everyone you pass on the street would torture and kill you if it benefited them in even the slightest way

[novu 🇵🇭 @evamuvon]

unhand me… faggot

[Big Wave Fan @KonaBigWavey]

@girlinterrupts9 My ex got off birth control and she turned lesbian. I’ll never date a girl on hormonal BC again

[mlx @mkiscg]

@timdv20 @BGroundNPC i think he'll do just fine

[mlx @mkiscg]

@Bigby_Wo_lf @GaaryWrld vous aimez les enfants juste assumez le c'est bon

[RELLY💫🇹🇹🇧🇧 @Relly_95]

Used his dad's bread to f*ck strippers and do drugs. Honestly fair enough

[AraiR&D @Litchi32135]

ちょうどマイカーの燃費が悪くて困っていたので助かりました！
参考にさせていただきます！

[Chadi @sb_chadi]

https://t.co/cwTQoLzQ3L

[mlx @mkiscg]

@sb_chadi @OpenAI Happy for your disclosure Chadi.
I know it's been eating your mind for the last months.
Hope actions are taken for the public interest

[Chadi @sb_chadi]

After 200+ days trying to coordinate disclosure of a critical ChatGPT container escape with @OpenAI, I'm going public.

I've documented the complete timeline of what happens when responsible disclosure fails.

📄 Full disclosure: https://t.co/GdUd8whNqg

The timeline:
- Feb 20: Reported via Bugcrowd → duplicate
- Mar 10: NEW container escape → no response
- Mar 17: VC escalation → no response
- Mar 31: CEO/CISO email → no response
- My submission DELETED from platform

200+ days total silence.

The vulnerability enables complete production infrastructure compromise:

Root access → SSH on 0.0.0.0:22 → Docker gateway → prod systems

Affects millions of ChatGPT users (Plus, Team, Enterprise).

I'm withholding the exploit technique (initial step) to prevent malicious use.

I consulted legal counsel across 3 jurisdictions.

I'm a 21yo security engineer. First major disclosure outside of web3. Just trying to do the right thing.

How long is "too long" when vendors don't respond?

Full technical writeup with evidence, timeline, and legal analysis:

https://t.co/GdUd8whNqg

Available for questions from researchers and journalists.

@OpenAI @sama

#InfoSec #ResponsibleDisclosure #ChatGPT

[Dragon Ball Games @dragonballgames]

DRAGON BALL XENOVERSE 3 is coming to PlayStation 5, Xbox Series X|S, and Steam in 2027.

#DBXV3
#DragonBall

[mlx @mkiscg]

@SalomeSeph33517 @ilias0005 @quit_lamise @romainreimois @Renoisdedroite Je suis plus renoies perso

[mlx @mkiscg]

@SalomeSeph33517 @ilias0005 @quit_lamise @romainreimois @Renoisdedroite Ah merdeeeee t'es un Boti bot
Suce mon e-penis

[mlx @mkiscg]

@SalomeSeph33517 @ilias0005 @quit_lamise @romainreimois @Renoisdedroite Ils ont peut être peur des noirs mais pas de toi arrête de ta cacher

[LaurieWired @lauriewired]

Modern DRAM is based on a brilliant design from IBM.

But, we're still paying for a latency penalty that's existed since the 60s!

In this video, I'm introducing my research project (Tailslayer) that immensely reduces p99.99 latency on traditional RAM!

By implementing a hedged read strategy taking advantage of (undocumented!) channel scrambling offsets, I've gotten as much as 15x reductions in tail latency.

The technique works across Intel, AMD, Graviton, DDR4, DDR5, x86, ARM, you name it.

Check out the C++ lib I wrote, watch the video, and try it yourself!