🚨NEW: The @USOCC and @FDICgov are moving to finalize a rule that would define the term “unsafe or unsound practices” in relation to bank supervision. This term has been undefined for years, and has relied on the broad discretion of bank examiners. The rule would require supervisors to tie alleged unsafe or unsound practices to an actual violation of law or material financial risk, making it harder to use vague reputational or procedural concerns to pressure banks over lawful customers, including crypto companies. It marks another significant step toward unwinding “Operation Choke Point 2.0.”

Phew, Grok Build is really thorough, pretty incredible. Relay feature for PasteLocal is done, pushing to Github now. And if you want to know what this adds, here's a bit more about it, this is a feature I really wanted in there, and honestly didn't really expect to have done this week. • Per-peer E2E encryption: clipboard data is encrypted individually for each paired device using X25519 + HKDF + AES-GCM (no plaintext ever leaves the client) • Durable persistence: relay state is now stored in an atomic state.json with proper TTL handling and compaction. Pending clips survive relay-server restarts • Safe compaction: fixed unsafe map mutation during expiration/compaction that could cause data loss or undefined behavior • Full bidirectional CLI: new commands: pastelocal relay send, inbox, fetch, and status, plus pastelocal-remote --relay --peer --send • Auto-sync: when watch.enabled + are on, meaningful clipboard changes are automatically pushed to paired devices • Improved DX: doctor checks are now only shown when relay is enabled, and the TUI shows basic relay status • Multiple review cycles: went through full implement → review → fix → re-review (effort 4), plus a final targeted regression fix round Try it out and please send any and all feedback!

The Schrödinger Equation Can Fold Phase Into Geometry. Density is only half the story. Here, the quantum phase itself twists into moving helicoidal ribbons, while self-gravity from the Schrödinger-Poisson coupling bends and compresses the wavefield into glowing caustics and vortex singularities. Tiny white pearls mark places where the phase becomes undefined topological defects drifting through a self-generated gravitational landscape. #QuantumPhysics# #WaveFunction# #SchrodingerEquation# #ComputationalPhysics# #ScientificVisualization# #Mathematics#

Hot take on today’s AI framework: these issues are so complex that even a pro-AI administration is deferring the hardest calls to Congress and the courts. This framework signals momentum and kudos to those who did such important work on it. But it still leaves open some thorny questions: -Federal preemption sounds clean, but could the undefined “traditional state police powers” carveout swallow it whole? -LLM copyright? Handed to the courts—leaving massive, open-ended risk on both liability and damages. SCOTUS likely won't take up the issue until there's a circuit split which will take many years. Meanwhile the race is on to file in district courts, as happened again in San Jose just this week (BMG case). Translation: clarity on paper, uncertainty in practice.

I’ve built HFT/exchange systems in three languages that sit at very different points on the safety/performance/ergonomics spectrum: OCaml, C++, and Rust. Observations and a practical comparison from production use: OCaml • Strong static typing and algebraic data types make illegal states almost impossible to represent. Protocol parsers, order book models, and risk checks are self-documented by types and function signatures. • The default garbage collector is a non-starter for predictable tail latencies. There are workarounds using disciplined zero-allocation techniques: custom core libraries, careful use of the [@ inline] and [@ unboxed] attributes, and a culture that treats any heap allocation in the hot loop as a bug. • Functional programming forces strategy writers to think in pure transformations of market data to fair values to orders. This style enables multiple forms of unit testing and makes offline model training pipelines easier to implement without major code changes. • The ecosystem for kernel-bypass networking and FPGA offload is thin; performant OCaml requires writing a fair amount of C interop or custom FFI. Compile times and binary size can also become painful at scale. • Engineering effort on type safety is a replacement for future engineering effort on debugging. We used to half-joke, “if it compiles, it works.” C++ • The most commonly used language in HFT because it offers maximum control. The writer can pinpoint every cache line, allocation, and branch. When the last microseconds matter, few languages can compete. • Industry standard for exchange connectivity, FPGA drivers, and shared-memory IPC. Virtually every low-latency NIC vendor’s API is written for it. • The cost is constant vigilance. Use-after-free, data races, and subtle ABI mismatches are permanent time sinks. Even with modern C++ features such as concepts, spans, and std::atomic memory orders, the cognitive load stays high. • Template metaprogramming offers some of the type-level guarantees of OCaml or Rust, but the error messages and compile times can be inscrutable. • Most of the “C++ is faster” advantage narrows when factoring in the engineering time spent hunting undefined behavior. Rust • Ownership and borrowing give the memory-safety guarantees of a garbage-collected language with the performance profile of C++. Zero-cost abstractions allow HFT system authors to write zero-allocation, lock-free, cache-aware code and the compiler will refuse to allow introduction of data races. • Excellent for the modern low-latency stack: DPDK/AF_XDP bindings, io_uring, shared-memory rings, and safe wrappers around exchange binary protocols. • The type system is expressive enough to encode many of the same invariants of OCaml, such as phantom types, newtypes, and state machines, without the garbage-collection tax. • The borrow checker still occasionally forces awkward redesigns of hot-path data structures, async/await is not yet as mature for ultra-low-latency work as plain threads/ busy-polling, and the ecosystem for certain HFT-specific libraries lags C++. • It takes time for the ownership model to click, after which mental bandwidth can be dedicated to strategy and latency. It’s much more difficult to build a high-frequency trading system that retains correctness and readability as it scales than it is to build one that’s fast. Good taste and developer culture can coalesce around a particular language, but the best teams possess these qualities independently, and can adapt freely and agilely to new technologies as they become available.

If you wanna switch to @Cloudflare Email Sending today, here's my prompt for you, as always I'm unaffiliated, not paid, not sponsored, but I like it, make sure you remove the space before the .com in the API url I added to avoid it becoming a link in this tweet: # Prompt: Migrate transactional email to Cloudflare Email Service Paste this into Claude Code (or Cursor, or any agent) running inside your project. --- I want to migrate this codebase's outbound email from its current provider (Postmark / SES / Resend / SendGrid / Mailgun / etc.) to Cloudflare Email Service (public beta, launched April 2026). Help me do this carefully. ## Context: what Cloudflare Email Service is A new transactional email API from Cloudflare. Endpoint: ``` POST .com/client/v4/accounts/{ACCOUNT_ID}/email/sending/send Authorization: Bearer {API_TOKEN} Content-Type: application/json ``` Request body: ```json { "to": "user@example.com", // string OR array of strings "from": "no-reply@yourdomain.com", // string OR {"address":"x@y","name":"Display"} "subject": "...", "html": "

...

", // optional "text": "...", // optional (one of html/text required) "cc": ["..."], // optional, array "bcc": ["..."], // optional, array "reply_to": "...", // optional, single string "headers": {"List-Unsubscribe": "<...>"} // optional, e.g. for newsletters } ``` Success response: HTTP 200 + `{"success":true,"result":{"delivered":[],"queued":[],"permanent_bounces":[]}}`. Failure: non-200 OR `success:false` OR non-empty `permanent_bounces`. Always check all three. Pricing: $5/mo Workers Paid plan + 3,000 emails free + $0.35 per 1k after. Roughly 5× cheaper than Postmark. No batch send endpoint — loop single sends. ## Steps you should follow ### 1. Verify prerequisites with me Before writing any code, ask me to confirm: - I have a Cloudflare Workers Paid plan ($5/mo) - I've onboarded my sender domain(s) in Cloudflare dashboard → Email → Email Sending → Onboard Domain (this auto-adds SPF/DKIM/DMARC + cf-bounce MX records) - I have an API token with `email_sending:write` scope (created at → Custom Token) - I have my Cloudflare account ID Don't proceed until you have these. ### 2. Recommend a domain reputation strategy Most apps should split senders across 2-3 subdomains so spam complaints on one don't drag down deliverability on others: - `mail.` or `members.` → transactional (login, receipts, password reset, in-app notifications) - `e.` → cold/recovery (abandoned cart, win-back campaigns) - `newsletter.` → opt-in newsletters with List-Unsubscribe headers Each subdomain needs to be onboarded separately in Cloudflare. Ask me which I want. ### 3. Audit existing email sends Use grep/search to find every place in this codebase that sends email. Look for: - The current provider's SDK class names, API URLs, env/config vars - Generic patterns like `mail()`, SMTP usage, `nodemailer`, etc. Group findings by email type/purpose (e.g. "magic-link login", "payment receipt", "weekly newsletter") rather than by file. Tell me what you found before changing anything. ### 4. Add a single helper function Don't sprinkle Cloudflare API calls across the codebase. Add one helper (provider-specific name like `sendEmailViaCloudflare()`) that: - Defaults `from` from a config var (don't hardcode) - Parses `"Name @domain>"` strings into the API's `{address, name}` object form - Accepts `cc`/`bcc` as either string or array - Accepts a `headers` dict (newsletters need `List-Unsubscribe` + `List-Unsubscribe-Post`) - Returns `bool` (true on success, false on any failure) - On failure, logs/alerts somewhere I can see (Telegram, Sentry, log file — match what the codebase already does) - Sets curl/fetch timeouts (5s connect, 15s total) so a stuck CF API can't hang the request - Treats `permanent_bounces: [...]` non-empty as a soft failure ### 5. Migrate one low-stakes email type first Don't migrate everything at once. Pick the lowest-stakes email type in the audit (something where landing in spam wouldn't lose me money or users — e.g. "internal admin alert", "profile photo rejection") and migrate just that one. Test it end-to-end. Confirm the email actually arrives. Only then propose the next migration. ### 6. Stop me from migrating login email yet If my codebase sends magic-link login or password-reset emails, do not migrate those to Cloudflare yet. Cloudflare Email Service is brand new (~1 month old at writing). Its IP/domain reputation is unproven. Login emails landing in spam = users locked out. Keep those on the current provider until at least 3 months of clean deliverability data on the lower-stakes types. Tell me this explicitly. ### 7. Suggest commit boundaries After each successful migration, suggest a focused git commit with a clear message. Don't bundle unrelated changes. ## Important caveats to surface to me - Beta product. Pricing isn't fully finalized. SLA undefined. Could change. - No batch endpoint. Mass sends (newsletters to 1000+ recipients) need a loop — at ~150ms/send that's ~2.5min per 1000. Fine for crons, bad for sync user-facing flows. - No bounce webhooks yet. Surface failures via the response body's `permanent_bounces` array. - Suppression list auto-managed. Hard bounces, repeated soft bounces, and spam complaints get blocked. Spam-complaint suppressions are hard to remove (anti-abuse). - No per-message logs/dashboard yet. Use the response's `messageId` for tracking if I need it. - List-Unsubscribe headers are passed through verbatim — Gmail's bulk-sender requirement still met, but only if I include them in `headers`. ## Your first action Before writing any code: do step 1 (ask for prerequisites) and step 3 (audit existing sends), then propose the migration order with a brief explanation of the reasoning. Wait for my confirmation before making changes.

It's still undecided on what #Bitcoin# will do. Losing this support level at $77,700 is going to be providing a significantly deeper correction to $74,000. If the markets hold here, I'm assuming we'll test the highs coming days to $82,700 and that will bring fun to the #Altcoin# markets for a bit.

Trump has undermined the rule of law and the integrity of the courts and weaponised the DOJ against his enemies, according to his detractors. Professor James Allan defends the President on all charges.