Understand the Signs and Symbols that Rule the World. Decode obscure and super-normal phenomena with plain language. Observer. Merope.
California
Joined May 2011
- Tweets66K
- Following8.9K
- Followers11.8K
- Likes11.8K
Vaxx didn't just lower IQ, it lowered the EQ. Emotion is different and seems to be managed by something else. This is the "Agent Smith" phenomena. Mention the shots carried tech to install a router and MAC address and the reaction will at once be anger. Internet of bodies.
Going to be easier to opt out and junk your phone.
🚨 THIS IS VERY STRONG
A content creator used Claude Code to discover that his Android phone had stored over 14,219 images captured by the front camera without him knowing.
And the most disturbing part is where they were stored.
They weren't screenshots or photos from the gallery.
They were real images taken by the front camera at different times of the day.
At home, at work, in the car, and even when he simply unlocked the phone.
How did he discover it?
He connected his Android to the computer and used Claude Code to investigate the device's hidden files.
He found images in system directories that normally don't appear in the gallery:
→ /data/system/users/0/faceunlock/cache
→ Directories associated with Google Play Services.
→ Over 10,000 files between normal photographs and infrared images used for facial recognition.
The most concerning thing?
Many of these images included date, time, and GPS location information.
The manufacturer and Google explain that facial recognition uses images to generate depth models and that they are then deleted.
But in this case, he found original files stored on the device.
He also discovered that some system services and apps with special permissions could have access to certain directories.
What did he do next?
→ Disabled diagnostic data.
→ Removed unnecessary camera permissions.
→ Cleared the caches he found.
But there's something you should keep in mind:
Not all images stored in these directories mean that someone has accessed them or that there's a data leak.
Even so, it's worth investigating what your own device is storing.
Want to check it?
You can connect your Android to the computer, make a backup, and ask Claude Code to search for front camera image files outside the gallery.
The AI can help you investigate system files that would normally go completely unnoticed.
Save this post. You might discover something you didn't know about your own phone 🗒️
👉 Follow @julia_coder_ for more AI, tech & privacy discoveries.
🚀 Get exclusive AI discoveries, newly launched tools, useful websites, GitHub projects, tech updates & resources I don’t share on X.
Join my Telegram channel to stay updated!
👉 Join Telegram : t.me/julia_coderAi
Space AI won't make sense until tech is 100x more powerful at 100x less power draw (swag numbers). Space based AI is out of reach of angry mobs, however.
Quick note for the reddit physicists who jumped in to "correct" @broudsov: they answered a different question. Yes, you can cool electronics in space. Satellites have done it for sixty years, at watts and kilowatts. The real question here is whether you can cool and power a gigawatt of GPUs easily and cheaper than a building in Texas can. Agreeing with the first says nothing about the second. The second is what matters because that's what @elonmusk is ultimately selling.
Here's the physics. On Earth, chips dump heat into air or water, and contact carries it away. Space has nothing to touch. Heat can only leave by radiation, one photon at a time, obeying Q = εσAT⁴. At chip-safe temperatures an ideal radiator gives you a few hundred watts per square meter. The ISS, the most sophisticated thermal system ever flown, rejects up to 70 kW with 422 square meters of ammonia radiator. Call it 166 watts per square meter, flight-proven. A single NVIDIA GB200 rack draws 120 kW. Sit with those two numbers for a second.
And the scaling is linear. Not approximately linear. Linear. Every watt of compute needs the same fixed patch of radiator, forever. The only lever in the equation is temperature to the fourth power, and silicon caps your temperature around 85°C. There's no clever move left. More compute means more square meters, more mass, more launches. "Scaling is not a problem" is exactly backwards. Scaling is the entire problem, and it never gets better with size.
"Starship makes launches cheap" doesn't beat the equation. It just changes who pays. The EU's own orbital data center study (Thales, Airbus, HPE) budgets about 2.5 square meters of radiator and roughly 5 square meters of solar panel per kilowatt. A 1 GW facility is 2.5 square kilometers of radiator and 5 square kilometers of array, tens of thousands of tonnes before you count coolant, pumps, and kilometers of plumbing, all riding the same rocket. The startup white papers admit it too: 4 km structures, hundreds of launches just to build the thing.
Then maintenance shows up. No, GPUs don't all die at year three. Plenty run longer. But at gigawatt scale, some fraction is failing all the time, and here's what happens on Earth when one does: a human walks down the aisle, finds the card, pulls it, seats a new one. In orbit, that human doesn't exist. You launch a machine that can locate one dead card at a grid coordinate inside a rack, extract it, and seat the replacement, in vacuum. That machine rides the rocket too. And when the servicing robot breaks? You launch a robot to fix the robot, or you write off the rack. If the answer is Optimus, fine. Now Optimus lives in a radiation environment and somebody has to service Optimus. It's maintenance all the way down.
"But the power is free." No. The sunlight is free. The collector isn't. Panels ride the rocket too, at 40-100 watts per kilogram of flight hardware, so a gigawatt of orbital solar is 10,000 to 25,000 tonnes of array. Then it starts dying on you. The best space-grade cells lose 10-15% of their output per decade in LEO from radiation alone. Cheap silicon loses 35-40%. Add atomic oxygen chewing surfaces, micrometeorites, 16 thermal cycles a day. NASA just spent $103 million bolting eight new arrays onto the ISS because the original wings aged out, and that was to keep 215 kW alive. A gigawatt needs 4,600 times that power system, with panel replacement launches on a schedule, forever.
And none of it works until the silicon survives LEO. Trapped protons and cosmic rays flip bits and kill chips. Commercial GPUs aren't rad-hard, so you add shielding: tonnes per module, which barely stops the heavy ions anyway, forces ECC and redundancy overhead that eats your effective compute, and sits like a winter coat between the chip and the radiator you were already short on. Every problem on this list makes the others worse.
Now notice the pattern. Cooling? Launch radiators. Power? Launch panels. Dead GPU? Launch a robot. Robot breaks? Launch another robot. Every single answer is "put it on a rocket," because the man selling the answer owns the rocket. When all you have is a hammer, every problem looks like a nail. When all you have is Starship, every data center looks like it belongs in orbit.
Add it up the way a CFO would. Radiator mass, array mass, shielding mass, coolant, pumps, robots, replacement GPUs, replacement panels, launch after launch. Every line item lands in the price per compute-hour. On Earth, air and water carry your heat for free, a technician with a screwdriver does your maintenance, and if you want dedicated clean baseload you build nuclear. Thorium, if you like. No rocket required. Even paying full price for power, terrestrial compute wins by a mile. The orbital pitch only survives while nobody prices it.
References:
Reddit rebuttal to @broudsov
reddit.com/r/elonmusk/commen…
Lumen Orbit Whitepaper (obvious VC money grab)
lumenorbit.github.io/wp.pdf
EU ASCEND Study
cordis.europa.eu/project/id/…
Decode the World retweeted
The pig was never banned for the worm. The worm was found in London in 1835. Sit on the throne of a small kingdom in the hills of the Near East around 900 BC and you will find the pig was banned for something you could see from the palace roof.
Your treasury is counted in sheep. The temple's ledgers count them by the ten thousand, and every one of them is a tax you can see walking. A sheep grows a fleece you shear every spring. A sheep gives milk, a sheep gives a lamb, and a sheep goes where the shepherd drives it, in a flock, to the altar, to the army, to the tithe barn, over the hills to the market you own. A sheep needs pasture, and pasture has an owner, and the owner answers to you.
The cow is better still. The ox pulls the plough that grows the grain you tax. The cow gives milk every day and a calf every year, and a bull on the altar is the prestige of the house that offered it. Cattle need land, wide land, the kind only a great house holds, so a man with cattle is a man with a landlord, and his landlord has you.
And then there is the thing in the yard behind every hovel in your kingdom.
It has no wool. It gives no milk you would drink. It will not pull anything. You cannot drive it to the temple in a flock, because it will not be driven, and nobody in your army wants to march to war behind it. It needs no pasture at all. It lives on the household's peelings, the acorns in the wood, the waste behind the house, and it turns the lot into fat. A sow throws ten piglets, twice a year, and they are bacon in six months. A family with a pig behind the house has meat and lard through the winter and has asked nothing of you, your priests, your pasture or your landlords to get it.
That is the problem. The pig is a democratic animal. It is the one source of meat in your kingdom that the ledger cannot see, and a man who can feed himself can afford to be rude.
So you want it gone, and you cannot simply take it, because there are thousands of them and they are in every yard. You need the people to give it up themselves, gladly, and look down on the neighbours who do not.
Which brings you to the second thing you can see from the roof. Down on the coast are the Philistines, the richer people, the ones with the iron and the ports, and they eat pork like Greeks. Their rubbish is a fifth pig bone. Yours is almost none. You did not plan that; the hills were always sheep and goat country. But it is a gift, because the easiest way to make a people is to tell them what they do not eat. Draw the line at the pig and every man in your hills is on your side of it and every man on the coast is on the other. Identity is cheaper than a garrison and it never mutinies.
You still need a reason, because people like a reason. Do not say the pig makes a poor man independent. Say it is unclean. Say the god finds it filthy. Do not explain why the cow, which stands in its own dung and carries a tapeworm of its own, is clean; nobody will ask, because the cow belongs to their betters and they already know better things are cleaner. Write it into the law with the hoof and the cud so it sounds like zoology. Your priests will enforce it for free, because it enlarges them, and in three generations nobody will remember it was ever a decision.
That is how the thing is done, and it was done again and again. In Egypt the swineherds were the one class in the country barred from every temple, and the workmen's villages behind the great building sites are knee-deep in pig bone, because the ledger never fed the men who cut the stone and the pig did. Every state that wanted its people dependent has found the same animal in the same yard and reached the same verdict.
The reason the modern reader has been given is the worm. Trichinella was first seen by a medical student with a microscope at St Bartholomew's Hospital in 1835, two and a half thousand years after the law was written. It is killed by cooking. Beef carries its own worm and was never banned. Goat carries brucellosis and sat on every altar. The hygiene story is a Victorian explanation bolted onto a Bronze Age tax policy, and it has lasted because it is flattering: it makes the ancient lawgiver a sanitary inspector rather than a man who had counted the sheep and could not count the pigs.
From the roof it was never about what the pig carried. It was about what the pig gave, to whom, without asking you first.
Your choices will depend on how much surveillance and control you want over your vehicles.
If you want zero remote control...pre-2004.
If you don't want MAC addresses in your tire pressure sensors...pre-2007 (shops face a steep fine for removing them but you can DIY)
I would go 4WD, everyone might be doing some offroading at the rate we're going.
An older suburban or Yukon.
Good people are everywhere.
A Boeing AH-64 Apache attack helicopter has no passenger cabin, no cargo doors, and no room for litters; it has only two narrow tandem seats built for the pilot and the gunner.
So when a critically wounded American soldier was bleeding to death on the ground in Ramadi, Iraq on June 30, 2007, one of the Apache pilots gave up his seat and rode on the outside of the helicopter through a combat zone.
Chief Warrant Officer Kevin Purtee of Texas and Chief Warrant Officer Allen Crist of Missouri, flying with the 149th Aviation Regiment, were on their final combat patrol of their deployment when an urgent radio call came in.
A young soldier from the 1st Battalion, 77th Armor Regiment had been shot through the face and arm during a fierce firefight near Donkey Island.
Forty agonizing minutes had already passed since the ground unit called for a medical evacuation helicopter, and the wounded soldier was running out of time.
Looking down at the smoke rising from the firefight, Purtee keyed his intercom and asked his front-seat gunner, Allen Crist, a question that is not in any Army flight manual.
He asked if Crist was willing to give up his armored front cockpit seat to the bleeding soldier and ride on the outside wing of the Apache back to the hospital at Camp Ramadi.
Crist answered with one word: Absolutely.
Why did they not wait another twenty minutes for a standard Black Hawk ambulance helicopter?
Because Purtee and Crist had seen good men die on the ground waiting for a ride, and they refused to watch another American bleed out while they had two spinning rotors overhead.
Setting the Apache down in the dirt, Crist unstrapped, jumped out, and helped three infantrymen lift the bandaged, blood-soaked soldier into the front gunner's seat and buckle his harness.
Then Crist climbed onto the left side of the fuselage, clipped a short nylon tether from his vest to a handhold, planted his boots on a six-inch metal walkway strip, and sat on the narrow stub wing right above the rocket pod.
He knocked twice on the cockpit glass with his fist, and Purtee pulled the Apache into the sky, flying at highway speed over hostile rooftops to the medical pad.
The next day in the hospital, with his shattered jaw wired shut, the surviving soldier took a notepad and wrote two sentences to the pilots: Thank you, and sorry for messing up your helicopter.
This is part of the reason the 2020 Macbook I'm writing this on is going to be my last Apple product.
And I was a die hard Apple dev since 1989. Steve called me after I took my company public. Other than him, I was one of the few public company CEOs using Mac.
Americans don't use WhatsApp because of a decision Apple made in 2013. We only know about it because the emails came out in court, and the whole thing came down to keeping your kids off Android.
It started with Eddy Cue, the guy who runs Apple's services. That April he emailed the team saying Apple really needed to put iMessage on Android. Google was reportedly trying to buy WhatsApp for $1 billion at the time, and Cue's pitch was that Apple already had the best messaging app, so why not make it the one the whole world used.
Craig Federighi, Apple's software chief, shut it down.
He asked how Apple was supposed to get Android users to leave WhatsApp when they didn't even have iPhone friends. So back in 2013, the guy running iPhone software was basically admitting WhatsApp already owned everybody who didn't have an iPhone. Then he got to what he was actually worried about. iMessage on Android would remove "an obstacle to iPhone families giving their kids Android phones."
Phil Schiller, Apple's longtime marketing boss, backed him up in another email thread in 2016, writing that putting iMessage on Android would hurt Apple more than help it. None of this was public until Epic sued Apple and the emails got pulled into evidence in 2021.
Now look at what that does to WhatsApp. The entire reason WhatsApp exists is that it works on any phone, so it wins wherever group chats are a mix of iPhones and Androids. Apple went the other direction on purpose. For years, every Android user in an American group chat showed up as a green bubble and their videos came through blurry, and the fix everybody landed on was buying another iPhone.
Tim Cook pretty much said this out loud in 2022. A reporter at a conference told him he couldn't send videos to his mom because she had an Android, and Cook told him to buy his mom an iPhone.
And it worked about as well as anything Apple has ever done. Nearly 9 in 10 American teenagers own an iPhone, and iPhones were 75% of phones sold at the big three US carriers in early 2026. If almost everyone you text has the same phone, an app whose whole selling point is working across phones has nothing to offer you.
Worldwide, Apple only sells about 1 in 5 phones. Most of the world's group chats stayed mixed, so they ended up on the one app that ran on everything, and WhatsApp blew past 3 billion users. Meta says more than 100 million Americans use it now too.
Apple finally added RCS texting with Android in 2024 and turned on encryption for it this May, and they still kept those messages green.
Apple basically let WhatsApp have the rest of the planet so it could keep American teenagers.
My theory as well.
99% of the time it's an inside job.
Fuck it. I'm going to say it.
I suspect the Binance hack wasn't North Korea. I think insiders may have been involved, and blaming North Korea is a convenient way to deflect scrutiny, shut down uncomfortable questions, and avoid looking closer to home.
Maybe I'm wrong, but the whole story deserves far more scrutiny than it's getting. Not every crypto hack needs to be blamed on North Korea.
When Zelenski started the "Revenue Share" plan with US politicians who voted money to Ukraine is when they started supporting it.
Decode the World retweeted
Yes, Palantir co-founders Alex Karp and Joe Lonsdale are very much involved with Chabad.
Palantir is Chabad.
No one will trust anything online very soon.
Grok bot found a hidden camera and microphone inside our Tesla taxi. my wife was in the back seat on the phone with her bank. the camera was pointed at her screen, every word she said was being transcribed on a server in Hong Kong, and someone was watching it live. i checked the account it uploaded to. same account. 212 cars.
⠀
the ride felt off. the driver used her name before she told him. i opened my laptop and asked Grok to scan every wifi and bluetooth device around us.
⠀
→ wifi → 14 networks
→ bluetooth → 23 devices
→ open hotspot → 'IPC_7F3A' → a cheap shenzhen ip-camera module
→ one unnamed bluetooth device → -41 dBm → not a phone
⠀
we drove 2.1 km. the signal never changed. it was inside the car.
⠀
→ device 1 → dashboard vent → inside the air freshener
→ device 2 → rear headrest → 40 cm from my wife's head → microphone
→ camera angle → the back seat, at phone-screen height
→ not a Tesla part → aftermarket, plugged in by someone
⠀
the car had free wifi. my wife was connected to it. so was the camera.
⠀
→ upload every 30 seconds → 47.243.***.18 → Hong Kong
→ 1.8 MB per upload → video and audio
→ audio → speech-to-text → keyword filter
→ keywords → card, code, password, pin, address
→ live stream → 1 viewer online → right now
⠀
i stopped scrolling. the 1 didn't go away.
⠀
i asked Grok to trace the account it uploaded to.
⠀
→ account → fl33t_***
→ 212 cameras → all moving → all in cars
→ 14 cities → mostly airport routes after 10pm
→ 31,000 rides recorded in 7 months
→ every ride auto-tagged → bank, crypto, home address
⠀
then Grok found our ride. and the one before it.
⠀
→ tagged HIGH VALUE → 4 minutes ago
→ transcript → her bank call → card ending 4417 → "the code from the sms"
→ a second recording of her → same car → 19 days ago
→ drop-off point on that ride → our home address
⠀
that's how the driver knew her name.
⠀
→ next stop → a telegram channel
→ 9,400 buyers → $25 per high-value ride
→ 3 rides from this same car already sold today
⠀
what Grok did next:
⠀
→ saved 41 files of evidence → timestamps and gps track
→ blocked card 4417 → bank fraud team notified
→ 11 minutes later → someone tried to spend $3,800 on it → declined
→ filed a safety report with the ride app → driver and plate
→ drafted a police report → ip, account, channel, both recordings
⠀
the driver was suspended 6 minutes after the report. we got out at the next light and walked home the long way.
⠀
211 other cars on that account are still driving tonight. most of them are waiting at airports.
⠀
if you take taxis at night, open your laptop next time you get in. it takes 2 minutes.
⠀
the prompt is in the comments. save it and send it to anyone who rides alone
Decode the World retweeted
So it turns out that the co-founder of the "Nazi" Azov entity in Ukraine is a rabbi who has served in the Israeli army and that one of the main funders of Azov has been Jewish oligarch Ihor Kolomoïsky.
The dam of lies has broken and a flood of truth will sweep zionism away. ⬇️
Oui. Natan Khazin est un rabbin juif d’Odessa. Il a servi dans Tsahal en Israël, puis a co-fondé Azov en 2014 avec sa « sotnia juive » de Maidan et d’autres volontaires.
Oui, l’oligarque juif Ihor Kolomoïsky a été un des principaux financeurs d’Azov (et d’autres bataillons volontaires) en 2014, avant son intégration à la Garde nationale.
I think the official storyline is fiction. However, it was an inside job.
El ataque a binance tiene una alta probabilidad de que haya sido bajo complicidad interna de programadores senior del exchange. Todos fueron engañados como niños por los hackers norcoreanos. 🤔
Segun cuenta binance, varios ingenieros de su equipo de programación mordieron al anzuelo de los hackers, no una, sino dos y mas veces. A continuación les cuento cómo segun Binance ocurrió la infiltración de los hackers, usaré nombres ficticios para el relato:
Todo empezó en junio de 2026 con Pedro, un programador del equipo de wallets. Pedro buscó en internet una herramienta de inteligencia artificial muy conocida para programar y la descargó. El problema es que no era la herramienta real, era una versión trampa con virus. El equipo de seguridad se dio cuenta, le cambió la computadora y le cambió todas las contraseñas. Parecía que se había solucionado, pero los atacantes ya sabían quién era Pedro y quiénes eran sus compañeros. Ya tenían el mapa de a quién apuntar después.
En septiembre le tocó el turno a José, también del equipo de binance. Lo contactaron por una página normal de buscar trabajo y se hicieron pasar por una empresa que le ofrecía empleo. Le hicieron dos entrevistas: en la primera le mostraron fotos y videos de una cuenta de redes sociales para que creyera que eran personas reales. En la segunda entrevista, por chat, le dijeron que descargara una “tarea” (un código) en su computadora de trabajo. José la descargó. Ese código era un virus muy avanzado y bien escondido que las herramientas de seguridad de la computadora no detectaron. A partir de ese momento los atacantes controlaban la computadora de José.
El 20 de octubre usaron la computadora ya infectada de José y una herramienta interna de inteligencia artificial de Binance para saltar a las computadoras de Pedro y de María (otra programadora del equipo de wallets). Además encontraron en la computadora de Pedro un “pase especial” (un token) que servía para instalar y ejecutar programas dentro de los sistemas importantes de la empresa.
Finalmente, el 29 de octubre, entre las 17:15 y las 19:56, los atacantes entraron a la computadora de María, usaron las credenciales y el pase especial que habían robado de Pedro, instalaron un contenedor con programas maliciosos y activaron el ataque contra el sistema que autoriza las transferencias de las wallets.
Según el relato de Binance, no fue un solo error. Fueron varios programadores que, en diferentes momentos, cayeron en engaños distintos y permitieron que los atacantes fueran avanzando poco a poco hasta lograr el acceso final.
Esto en mi opinión está bien raro. Ni yo que no soy experto en ciberseguridad descargo algo en mi PC que me diga un tercero que no conozco.
¿Qué opinan ustedes? 🤔
Decode the World retweeted
Comment: "Remember when Pat Robertson ran for president (no comment on his qualifications), and his campaign imploded when he used the term 'international bankers'? From that point on, he was labeled 'antisemitic', and he'd never even used the 'J' word."
Response: That's exactly what happened to me, except that I simply used the word "bankers" on a social media platform to describe a bunch of mortgage-peddling white-collar criminals who had tried to rob my wife and me on a home loan in New York (they handed us a payment schedule of nearly a million dollars for a $200,000 property loan).
The words "Jew" and "Zionist" were never used; I called them "bankers" without qualification. Yet it wasn't very long before a couple of muckraking Jewish "journalists" decorated a couple of libelous outhouse rags, "The Baffler" and "The Forward", with spiteful hit pieces. Learning of this, certain pets of Israel-first donut boy Jimmy Wales, leader of the Wickedpedia Cult, began accusing me of "antisemitic dog whistles". My widespread cancellation soon followed.
Apparently, many Jews consider "banker" a synonym of "Jew". They don't seem to care that this amounts to taking full responsibility for every outrageous atrocity bankers have ever committed, and they don't seem to mind ruining someone's economic prospects and reputation with false accusations. It almost seems as though they are unable to admit wrongdoing of any kind, perhaps because it might count against their exemplary moral status as "the chosen".
Had I the chance, I'd have cautioned them against doing that to me. There's nothing to be gained by calling non-enemies "enemies" just to be nasty; it simply isn't rational. But I never got the chance, as I was summarily banned from Wickedpedia by a Jimmy Wales flunky calling himself "JzG", aka "Guy Chapman". Even after JzG lost his "administrator" privileges for a long history of spiteful mischief, Wales stuck to his guns and disallowed any corrections of its various errors and omissions.
There's a lesson in this: once a Jew or two pop their corks on you for any reason whatsoever, stiff necks and ethnic solidarity do the rest. The entire group acts as a collective, and one is powerless to stop them. Once any Jew has gone public against you with an accusation of "antisemitism", nearly all Jews feel obligated to side with him and against you whether or not the accusation was justified. Even if you're as jolly as Santa Claus and as morally pure as the driven snow, an "antisemite" you are, and an "anstisemite" you will forever remain!
In other words, there's no need to feel bad when any of several thousand rabbis accuses all Whites, including you, of being an "antisemite" and therefore deserving of annihilation as "Amalek". There's nothing you could have done to stop it.
