cmd+, and it transcribes on release.

Nowhere close to claude/codex experience. Unusable dev experience

this is correct and wide way to look at replicated machines.

Many on HN just lack vision and love to hate on things. "Infamous dropbox comment".png

You can wake up with your bank / broker / PayPal balance = 0, what do you do?

→ “AI generates slop, false info, deepfakes make ppl look bad, therefore AI = bad.”

Same vibes.

You can wake up with your bank / broker / PayPal balance = 0, and there is nothing you can do to protect yourself from that scenario. Only replicated state machines (or L2s built correctly on top of them) even attempt to close that attack surface — and they’re still not finished.

In 10–20 years the world will run on government-run CBDCs, and your relationship with your bank/broker will finally be protected by actual cryptography and replicated state: xln.finance. That’s when crypto reaches its real bloom. Right now it’s nowhere close to being mature enough to judge.

If you’re a trader, jokes on you — you were never “in crypto.” You were just passing through.

The only people who are actually in crypto are the ones who build: smart contracts, consensus, p2p layers, replicated state machines.

Everyone else is just cheering from the sidelines (usually for the wrong team).

>We should demand privacy, not laugh at the notion of privacy.

Recently got m3 ultra 512gb studio. LM Studio runs frontier models routinely. Going local is the ONLY way. That's all you can do. "Demanding privacy" is security theater. Act accordingly.

why imagine? The world already functions exactly like that. Talk on Tg like every chat is summarized every 24hrs and monthly (with cheap LLM and then with strong ones if signals found), and it reports to all kinds of interested intel agencies.

Same for openrouter. everything that leaves your device plaintext = public. Period. No hopes.

Oh, here we go again. JavaScript brings mass assignment back. My efforts went in vein. Strong params, pls!

Think Lightning, but on EVM, with credit that’s provable and enforceable. No sequencers. No DA risk. O(1) per-hop scalability.

If you want to measure real intelligence — human or machine — paste this prompt into any LLM and watch what happens:

Prompt: “Comprehend the following concept in full depth. Derive all its implicit implications, design questions, and systemic consequences. Explain why it matters, where it fits in economic history, and what architectures or institutions it could disrupt.”

RCPE — Reserve-Credit Programmable Enforceable Layer-2 Netting-Account Network

Solves Coase theorem and Diamond Dybvig runs. Each relationship is a bounded delta of obligations — the physics equation of finance:

−Lₗ ≤ Δ ≤ C + Lᵣ

RCPE ⊃ { FCUU, FRPE }

FCUU Full-Credit Unprogrammable Unenforceable

(−5000 BCE → Now) C = 0 Δ ∈ [−Lₗ, +Lᵣ]

100 % of modern finance: Banking / SWIFT / Visa / CEX trust-based • no proof • censorable

[−−− Δ −−−]

FRPE Full-Reserve Programmable Enforceable

(2015 → 2020) Lₗ = Lᵣ = 0 Δ ∈ [0, +C]

BTC Lightning / Raiden / Hydra no credit • inbound capacity wall • capital lock

[==Δ=]

XLN (RCPE) ⊃ { FCUU, FRPE }

Δ ∈ [−Lₗ, C + Lᵣ]

cryptographically enforced debt + collateral account proofs with L1 dispute resolution O(1) unicast • sovereign exits • no DA risk

[--==Δ=--]

Example - prompted with Sonnet 4.5: https://claude.ai/share/99453e1a-1ce4-4a73-aa31-36b8bea7520c

Looking for VCs, co-founders, market makers. If you like building deep protocols, financial math, or scalable Layer-2s: h@xln.finance

is there any similar game or is it first 3d in-browser game with amazing graphics?

Something claiming over 20-30 tps onchain is usually a big blocker. Big blocker design is well recognized as insecure: no end user is able to run a full node locally, only datacenters are able to keep up with 100k tps load. Which diminishes entire purpose of creating a blockchain. Could have been a database with 100k tps or 3-of-4 validator multisig like Hyperledger, wouldn't matter.

The spec itself made mistakes:

• Silent account hijack via “Connect this provider.”

• Redirect leaks of code (via Referrer) or access_token (via #hash).

• CSRF because state was optional and often ignored.

The point is: these aren’t obscure edge cases, they’re structural issues baked into the protocol.

I have an old writeup on that and solution to it https://sakurity.com/oauth - better analyze it with LLM if interested in authorization protocols

From my personal experience, SSRI (zoloft) felt like a temporary coffee-like stimulant. Psilocybin (or easier to handle synthetic analog 4-aco-dmt) provided short-acting relief from depression and some new perspectives. But ketamine is truly a magic pill if done right. After glow is about a month, and the trip takes 2-3 hrs max. FDA-approved, see Spravato. I feel like at some point ketamine therapy at scale would make SSRIs obsolete, it's just better and faster.

https://www.youtube.com/shorts/6dcc0hLe0mc

frame rate was too bad so i just bought dasung paperwhite :)