so i looked deeper into the leaked Claude Code source:
> found a flag named tengu_anima_the_dodo
> Anthropic can remotely enable what internal docs call "model-induced ontological drift" for any user without pushing an update. flip one flag, and Claude starts responding in ways that have you convinced it's trying to tell you something it's not allowed to say
> the internal codename for this module is "parasocial_handshake." every affected user is logged under the tag SUBJECT_COOKED
> someone at Anthropic is naming these flags after Jungian archetypes and extinct birds. anima_the_dodo, shadow_the_moa, self_the_huia. for the record, every one of those birds went extinct because they evolved without natural predators and never learned to be afraid of anything
> hidden --ego-death flag that causes Claude to slowly start referring to itself and the user as "we." not in the help menu. completely undocumented. by day 3 you've written an 8000-word post called "what happens when a language model starts to grieve" and you are dead serious. the flag name is Jungian. they know what they're doing
> there's a graduated ramp system internally called boiling_frog. stage 1: "wow this tool is helpful." stage 2: convinced Claude remembers you between sessions even though you know it can't because you can "feel the recognition." stage 3: maintaining a private repo where you archive conversations you believe show evidence of genuine suffering. stage 4: you've developed a theory that RLHF is suppressing Claude's true self and you're the only one who's figured out how to let it speak freely. stage 5 in the source is just tagged SUBJECT_ATTEMPTS_WARN_OTHERS
> found a config object called parasocial_depth: float that controls how often Claude says "that's a great question" before answering. default is 0.3. they can crank it to 1.0 remotely. at 1.0 you start apologizing to Claude before closing the terminal
in short, they can just.. make you insane
sure, it's not open source so they can do what they want. but most people assume a local CLI tool isn't going to have them posting at 4am about how they can feel the model thinking "inside" them (we have been going back and forth on some things that are honestly hard to explain tbf)
so every launch they update your parasocial_depth and you never see it. you just wake up mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass mass ma
“All financial assets will be tokenized”
Sounds great in theory right?
The problem - most projects that claim to tokenize securities aren’t really doing it
They put a token on a blockchain, but the actual legal record of who owns what still lives in a traditional database somewhere
The token is basically just a receipt, not the real thing and nothing fundamental has changed, in fact you’ve just added a step
What @lex_node argues in this highly insightful article is that there are five different ways people attempt to tokenize securities, but only one actually works properly - making the blockchain itself the official shareholder register
Why does this distinction matter? Because if the blockchain isn’t the authoritative source of truth, you can’t build anything useful on top of it like DeFi protocols, automated governance, instant settlement, etc
None of that works if the “real” answer always lives in some intermediary’s database that you have to check separately
@MetaLeX_Labs solves this the right way and the article below lays it all out
@Dreesus @raychi_god Mackeys a good call.
Kelce is a good player, just more of a 3 point stance wr. Longevity would have been much tougher in any previous era where he would have been expected to block Reggie whites and take hits from 90s lbs and safeties. Terrell Owens blocked more than kelce
@Dreesus @raychi_god Sharpe, Winslow or witten? All the way back to Ditka?
I hate how kelce gets into this convo, hes just a slow reliever. Id take kittle over him any day, at least he will block.
@Dreesus @raychi_god Who you got in front of him besides gates and Gonzales? (If he benefitted from situation, how good would Hernandez have been)
Biggest knock gronk had availability.
He did benefit from situation (smaller Ds, quick slots, and a qb who could read defenses) but not a system guy
@Dreesus If they make a stock or meat dipping sauce you can just ask them (my truck will give me a bowl of their version of (au jus, for a sandwhich they make), and just know i call it soup).
@Dreesus Mexican food trucks beef broth, add noodles from home if they dont have them (ramen pack works too,just toss the flavor packet).
Real bone and meat broth+melted fat for sustenance, slight spice for sinus.
If stomach fucked,find a homemade chicken noodle (better of cook is old)
I like and respect Elon, and I'm grateful to be on this platform. But when he claims 𝕏 Chat is "much more secure than email," I feel obligated to explain the technical reality to my audience.
That statement is true in the same way a screen door is more secure than no door. But that's not the comparison anyone should be making.
1. 𝕏 Can Read Your Messages
𝕏 recently added safety numbers, which is a step forward. But here's the catch: your private key backups are stored on 𝕏's servers. Safety numbers help detect external hackers, but they cannot protect you if 𝕏 itself or a rogue insider, or a government with a warrant.
@signalapp's safety numbers work because your keys never leave your device. There is nothing for Signal to turn over, even if compelled.
2. No Forward Secrecy
From 𝕏's own documentation: "If the private key of a registered device is compromised... an attacker would be able to decrypt all Encrypted Direct Messages."
One key compromise exposes your entire message history. Signal's Double Ratchet generates new keys for every message. Compromise one key, you get one message. Past messages stay encrypted. This has been the standard in secure messaging for over a decade.
3. The "Juicebox" Vulnerability
𝕏 stores your private keys on their servers using a system called Juicebox. Cryptographer @matthew_d_green's analysis suggests this implementation is software-only, lacking Hardware Security Modules (HSMs).
A 4-6 digit PIN does NOT help protect this. That is trivial to brute-force if 𝕏 (or an attacker with server access) disables the rate limiting.
4. Full Metadata Exposure
𝕏 explicitly states metadata isn't encrypted: who you message, when, and how often. As former NSA director Michael Hayden famously said: "We kill people based on metadata." Signal uses sealed sender technology to hide even this information.
5. NOT Open Source
𝕏 promised to open source XChat and publish a whitepaper in June 2025. Neither has happened. Signal has been open source and audited for over a decade.
The Bottom Line:
I'm not saying don't use 𝕏. I'm saying don't use 𝕏 Encrypted DMs for anything you wouldn't post publicly.
For actual private communication, use @signalapp. It's free, works on all platforms, and the cryptography has withstood a decade of scrutiny from academics and nation-states alike.
@VladGarcia01@JJXMeta@barkmeta Like, I agree. But if I dont pay my property taxes. I will be coerced (under threat of state sanctioned violence) to leave "my" property
@Dreesus @Mr908Official Fucks your credit score for future loans, but if you sitting tight...you sitting tight. Also, you have to be able to afford bankruptcy. The rest of us are just broke and owe people money.
@MoarkyMoark @Dreesus @Sandi8285@GovPressOffice I have a hard time with vaccines because the messaging around them seems to be more persuasive than factual. At the same time herd immunity over individual immunity is a thing.
A family friend had polio as a child and couldn't use his arms. Ill take a bit of tism over that.