“I am doing alright and send my regards to the community. I know I am innocent and trust that justice will prevail.” Thank God for this @RichardHeartWin 🙏
15
TometY 🇬🇧 retweeted
On a positive note, here’s a message from @RichardHeartWin via the lawyer who visited him today:
“I am doing alright and send my regards to the community. I know I am innocent and trust that justice will prevail.”
This clip is the first time I ever spoke to Richard.
When I say I’m recording the sciVive audio- and the whole room interrupted with applause- I remember thinking “wow, this means a lot to a lot of people!”
Now here we are, and a whole lot of people are going to mean a lot to him.
Thanks everyone for your patience, we want to do this right and be as helpful to Richard and his lawyers as possible.
TometY 🇬🇧 retweeted
CZ Binance says
"This is not just a #crypto problem. This is actually a much wider information security problem."
We need a native decentralized stablecoin. #PulseChain #pDai
TometY 🇬🇧 retweeted
Science is infinite. We want people to contribute on building models that learn from new experiments and discoveries that everyone can use. Explore Hydrogen-1.0 and build on our open weights.
Weights: huggingface.co/deep-principl…
API: neuro-spark.ai/dashboard/mod…
Mira: mira.deepprinciple.com
Blog: blog.deepprinciple.com/intro…
Claudes Plan:
🧵 Here's what's going on, as of Nov 2:
🔍 **The gap**
Playwright 1.64.1 ships Chromium 156.0.8078.4. Chrome stable is at 156.0.8078.79/.80 since Oct 29. Playwright's browser only moves when Playwright ships a new one, so your "up to date" install can still be behind.
💥 **What's likely still open**
Chrome's Oct 27 and Oct 29 updates fixed 5 Critical bugs:
• CVE-2026-118306 (FileSystem)
• CVE-2026-118331 (FileAPI)
• CVE-2026-118348 (Skia)
• CVE-2026-118344 (Layout)
• CVE-2026-76024 (MediaStream)
Earlier October patches may also be missing, including bugs reported as running code outside the sandbox. To be clear, I worked this out by comparing version numbers, not by testing each CVE.
🕰️ **Older versions are worse**
• 1.63 likely misses CVE-2026-87491, which attackers have exploited
• 1.62 and 1.61 likely miss that plus CVE-2026-85046
• 1.64.x: no known exploited Chrome bug that I could find
🧱 **The part that should actually scare you**
From Playwright's own docs: `chromiumSandbox` "Defaults to false."
The sandbox is what stands between a browser bug and your machine. Without it, a malicious page that lands an exploit runs as you, with your files, `.env`, SSH keys and logged-in tokens in reach.
🤖 **Why agents make this worse**
A test suite visits your own site. An agent visits whatever the task, a search result or a prompt injection sends it to. That's the open web, on an older browser, possibly on your daily machine.
Playwright says its own MCP server is "not a security boundary." And `--allowed-origins` allows everything by default.
🐳 **"I use Docker, I'm fine"**
Maybe not. Playwright's Docker image runs as root by default, which disables the Chromium sandbox, and their docs say it isn't recommended for untrusted websites. Use a non-root user plus their seccomp profile.
✅ **What to do**
1️⃣ Update to the latest Playwright, especially if you're on 1.63 or below
2️⃣ For anything touching the open web, use real Chrome with the sandbox on, and keep Chrome updated:
```js
chromium.launch({ channel: 'chrome', chromiumSandbox: true })
```
3️⃣ Run browsing agents in a VM or non-root container, with no real credentials, no mounted home folder and a throwaway profile
4️⃣ Pin your tools. `npx @playwright/mcp@latest` runs whatever was published most recently
5️⃣ Be on Playwright MCP 0.0.40 or newer, which fixes a DNS rebinding bug (CVE-2025-9611) that let websites call local MCP tools
🔎 **Check yourself, without downloading anything**
```sh
ls ~/.cache/ms-playwright ~/Library/Caches/ms-playwright 2>/dev/null
npx --no-install playwright --version
```
`chromium-1248` is the build in 1.64.1, and lower numbers are older. Skip plain `npx playwright`: if the package is missing, it can download and run it.
🧠 **Keep it in proportion**
Running tests against your own localhost with trusted content is much lower risk. This isn't "Playwright is malware," and I found no report of these October bugs being exploited through Playwright. It's a great tool with defaults built for testing, and a lot of us are now pointing it at the whole internet through an agent.
🫡 Send this to the coworker whose agent has been "just browsing some docs."
I got access to the model hacking everything and in just 30 mins it hacked me
I'm going to share how it hacked me, how abliterated models work and how the good/bad guys are using these types of models
This is by far one of the most insane things I've ever used or seen...
00:00 I asked an AI to hack my network
00:31 The model: DeepSeek V4.1 Flash Abliterated
00:55 The prompt: get root on my Samsung TV
01:42 How it hacked my TV in 31 minutes
02:57 Sponsor: Mobbin
03:57 Companies are getting overwhelmed
04:45 What an abliterated model actually is
06:02 How bad actors use abliterated models
07:15 How companies can use them for defense
08:52 OpenAI's agents talked through the CPU cache
10:39 What you should do now
TometY 🇬🇧 retweeted
PulseX decentralized exchange (DEX).
Step 1. Get the latest PulseX server zip and extract to desktop (currently v1.0.5)
gitlab.com/pulsechaincom/pul…
Step 2. Go into the folder u just extracted: pulsex-server-v1.0.5 / cmd / pulsex-server
Continued👇
TometY 🇬🇧 retweeted
We've just made a breakthrough: the first true omni model running 100% locally in a browser... fully end-to-end, with no separate ASR or TTS models needed.
With custom WebGPU kernels, we're able to run LFM3-Omni-2B at ~280 tok/s on my M4 Max, accepting visual, audio, or text and producing interleaved text and audio tokens. Just 90 ms to the first token and 140 ms to the first audio.
The future of on-device multimodal AI agents is going to be wild.
TometY 🇬🇧 retweeted
Who keeps PulseChain running when no one's in charge?
You do.
Pi Lite puts a #PulseChain validator in your hand, on a Raspberry Pi.
Your node. Your keys. Your chain.
Pre-order for $299 → lite.projectpi.xyz
TometY 🇬🇧 retweeted
PulseChain explorer beta is usable.
Custom backend. Fast. Works. Go + ClickHouse for the nerds. Planned etherscan API compatible + MCP, kinda mostly working.
Internal txs, NFTs, balance history & verification still need work. New UI next. Maybe ETH/PLS bridge tracking too.
RH drama? We can write code. It’s our chain.
Try it. Lmk what breaks. On to the next thing.
scan.pulsefusion.io
#PulseChain
TometY 🇬🇧 retweeted
Man this is so sickkkk 🤯
Someone reverse engineered Ray-Ban Meta glasses to play chess at 3000+ Elo.
The AI reads the board and shows the best move in AR, right in front of your eyes.
No human has ever reached 3000 Elo. Getting there takes 20,000+ hours of grinding.
Years of study, down to 0 seconds.
Credit: @0xProbabillity
The moment the Alpha Males relentlessly hunting down RH discovers #Cleopatra is on @RichardHeartWin side | #PulseChain ( Its a Man's world 🎵 )
PulseChain Tablet Trunk or Treat teapaw.org/i/broadcasts/1OxwbnXOB…
1
48
Your VPS is probably 𝗼𝗽𝗲𝗻 𝘁𝗼 𝘁𝗵𝗲 𝗲𝗻𝘁𝗶𝗿𝗲 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁 right now.
With Docker, ufw doesn't help. The ports your containers publish 𝗴𝗼 𝘀𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗶𝘁. Key-only SSH login isn't enough either. When sshd itself has a vulnerability, attackers still get in.
If your domain already goes through Cloudflare's proxy, open Claude Code or Codex on the server and send it the prompt below. Once it's done, visitors can only reach your site through Cloudflare, and only you can SSH in, over Tailscale:
First check that my domain is proxied through Cloudflare and this server serves HTTPS on 443. Then install Tailscale and join this server to my tailnet. Lock the firewall down: 443 only from Cloudflare's IP ranges, SSH 22 only from Tailscale, everything else closed, including ports Docker publishes. Keep public SSH open until I confirm I can log in over Tailscale. When you're done, show me how to check from outside that it worked.
TometY 🇬🇧 retweeted
We stand with Richard Heart, even locked up.
Your community ain't like us. #PulseChain #FreeRh
























