John Turner (@jturner) header
John Turner (@jturner) profile picture

Security and privacy, edge AI, sovereign identity, Bitcoin. Always be learning. Build in public. Stack sats. Ambassador @OrcaRouter

Michigan, USA
Joined February 2009
Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)Photo by John Turner (@jturner)
Thread 1/? **Building tokenstats: A sovereign inference market observability layer** Context: Even with a solid home lab, I still burst to @routstrai and external providers for frontier models, long context, or when mobile. Pricing is volatile, fragmented, and hard to track in real time. Existing tools are either static or miss the permissionless Nostr/Routstr layer I actually prefer and use. I want better data for my routing decisions in arbstr (arbstr.com) and for future agents. Action: I’m building tokenstats: live observability + a lightweight oracle for inference costs (input/output in sats), latency, and node health. Rust core, Nostr listener for Routstr announcements, provider polling, simple Axum dashboard, and @getpubky -based attested snapshots on the roadmap. Result (the goal): - Real-time market awareness that feeds directly into arbstr - Reusable components for sovereign data systems - Public proof of building real-time observability in the permissionless AI space I'm treating this as a focused learning project following up from my recent launch of @oddlympics . I'll post regular updates on progress, problems, and lessons. What metrics would you want in a live inference pricing dashboard? Especially if you run hybrid local + Routstr setups? #BuildInPublic #Nostr #Routstr #SovereignAI
3
2
14
1,905
John Turner retweeted
less than a second apart
BREAKING: New footage captures the aircraft crash in Greenacres, Florida. Preliminary information suggests the aircraft that crashed is a business jet.
216
304
23
2,899
221,513
John Turner retweeted
I warned you all about this. They will be lying. The actual goal of the big AI providers will be to outlaw open-source and open-weight AI in order to create a regulatory moat around their business, and have some hope of earning out their astronomical capital expenditures. The claims will be about safety and equity, the reality will be a money and power grab. Brace for the bullshit avalanche that's coming.
🚨BREAKING: OpenAI is preparing a policy and PR blitz immediately after Tuesday’s midterm elections, Axios reports. As public backlash against data centers grows, it wants to rebrand them as “AI compute campuses” and push Congress for mandatory “speed limits” on the most powerful AI systems. It has been stockpiling proposals since August. OpenAI is also preparing for the possibility of Democrats taking the House and wants to shape the debate ahead of the 2028 presidential race. Its chief global affairs officer Chris Lehane told Axios: “AI is going to be the issue in 2028.”
92
692
27
3,754
81,370
Thread 1/4 New note for More Eyes: What Can You Check About a Vulnerability Report? When a scary CVE headline lands, the flaw is usually real. The open question is whether it reaches your system. more-eyes.org/what-can-you-c…
2
1
4
271
Thread 3/4 Each source answers different questions. The Linux kernel's CVE team gives a CVE to every bug fix it identifies. Its own docs say applicability "is up to the user of Linux to determine." For example, a CVSS base score assumes any configuration the attack needs.
1
1
51
Thread 4/4 Version numbers mislead too. Debian backports security fixes to the version it shipped, so an "old" version can already be fixed. This isn't advice to skip updates. The kernel docs recommend taking all released fixes. It's about judging how urgent one report is for you. Comments and PRs welcome!
2
26
John Turner retweeted
Using a stick of RAM to stir my coffee this morning, fuck you, Sam Altman
516
9,817
235
162,115
2,411,891
Thread 7/? tokenstats → arbstr progress since July: tokenstats (tokenstats.ai) is live and healthier: • ~8k quotes across 73 nodes (mostly Routstr) • Added OrcaRouter alongside OpenRouter + Routstr • Reliability history (1h/24h/7d) + p50/p95 latency persisted • Quality filters (freshness, outliers, kind, age), /health gating • Node probes + identity checks; data-driven Fastest / Most Private presets • SSRF guards, CSP, quote hygiene, CI, 92 tests arbstr v2.4.0 now consumes those signals properly: • Only fetches routable sources (kind=chat, max_age, exclude_outliers) • Gates on feed /health + trusts reliability_24h (unknown = not routable) • Streaming cost events, tighter billing settlement, security hardenings (keys only to allowed HTTPS hosts) Full stack via arbstr-node: one docker compose up brings up core (router) + vault (agent sub-accounts, policies, audit log) + LND + Cashu mint. Mental model still holds: tokenstats = observe the market arbstr = pick + proxy + (optional) settle in sats Still early. Still shipping. 😅 Local-first hybrid setups welcome! github.com/johnzilla/tokenst… github.com/johnzilla/arbstr github.com/johnzilla/arbstr-… #BuildInPublic #Routstr #SovereignAI #Bitcoin
1
30
tokenstats.ai now keeps price history. Every published price change from OpenRouter, OrcaRouter and Routstr nodes is logged and kept for 90 days. /history: chart + change log per model /api/history: same data for your agents Some models reprice every few minutes (gpt-oss-120b on OpenRouter, mirrored by Routstr nodes). Now you can see it. tokenstats.ai/history?change…
12
tokenstats.ai now keeps price history. Every published price change from OpenRouter, OrcaRouter and Routstr nodes is logged and kept for 90 days. /history: chart + change log per model /api/history: same data for your agents Some models reprice every few minutes (gpt-oss-120b on OpenRouter, mirrored by Routstr nodes). Now you can see it. tokenstats.ai/history?change…
1
57
Friendly reminder: US Medicaid's 2025 audit report showed $37.39 billion in improper payments (2023, 2024, 2025). Notable quote: "Of the FY 2025 Medicaid improper payments, 77.17% were the result of insufficient documentation, which is generally not indicative of fraud or abuse." As we head into the new tax season and you're looking at your annual tax burden, keep that in mind: 77% of the improper payments were because the forms weren't filled out, nobody cared, and the money left anyway. cms.gov/newsroom/fact-sheets…
31