ED ⚡️ 🍯 🦡

Lexus says its upcoming all-electric LFA supercar will use vibrations and other sensory feedback to mimic the feel of a combustion engine. "We’re not just wanting to replicate the sound of the engine: we want to redesign the sound itself so the car feels more alive and authentically connected." The production version of the car is expected to be unveiled at the end of this year/early next year. Concept unveiled in Dec 2025:

Fuck European Parliament Fuck Chat Control Use Signal

The Russians obviously took him out but the U.S. doesn’t want to wage war with Russia so they’re claiming it was a “sudden illness”. This cover up reaction by the U.S. tells us everything. We clearly don’t feel capable to take on Russia or another power militarily. Tables have turned. Every U.S. leader advocating for war should be worried for their lives. The US has been assassinating leaders with impunity because no one wanted to take the U.S. on. Now tables seem turned. We may see an increase in assassinations and honestly….what would we even do about it besides cover it up each time?

Great site, Stephan but sadly, at this point, it won’t help because it was never about spam. It was always about CSAM. And ultimately, that was about non-contiguous data. Unholy images could always be put in the Taproot witness or anywhere else on the blockchain and no one was really losing their mind over it. At least not to this degree. It wasn’t until Core opened the OP_RETURN limit and allowed spammers the option to pay four times the price to put data in OP_RETURN and thus put it on-chain in the best possible manner, so it doesn’t bloat the UTXO set and can be pruned that suddenly everyone lost their mind. Including Pope Luke. Technical people were completely at a loss as to why they were losing their minds. You could already put images in the witness data. What makes OP_RETURN so different? Why are you losing your mind over this OP_RETURN limit? Why is opening up a path that is 4X more expensive and less harmful to the UTXO set so UNHOLY? Slowly, we uncovered the reason. It was because of CSAM and non-contiguous data. Apparently, the all-high ruler declared that an image broken up into 520-byte chunks is canonical and therefore allowed. But if you remove those push-byte opcodes and put it all on-chain continuously, then it becomes unholy because the image can be scanned directly. Sadly, when we pointed out that all this data is fully obfuscated using an XOR key such that no antivirus software could read whatever image was inscribed on-chain without first obtaining the XOR key, nobody really listened. Apparently a program can grab an XOR key and decrypt the contiguous data and that is UNHOLY -- BUT a program removing 8 bits of data every 520 bytes to re-constitute an image is cannon. Someone please...make it make sense. And the whole thing went downhill from there. Somehow, they made a golden calf out of an OP_RETURN size-limit increase, when in reality, the spammers were barely using OP_RETURN. (in so far as aggregate bytes of trash put on chain) Currently, 99% of their OP_RETURN usage falls within the 83-byte limit and will be mined within BIP-110 blocks. The irony is so thick, you literally cannot make this stuff up.