What 🫣🫣 try.cloudflare.com/ What a time to be alive man….

Most tech giants in the 2000s built their infrastructure and product as one entangled unit. Amazon had the foresight to separate out AWS as an API layer, of which Amazon retail was the first of many users. Today, AWS generates more profit than all of Amazon's other business lines combined. Hyperliquid is built with the same philosophy. Housing all of finance requires thoughtfully designed, open financial primitives. Each primitive should obey the Unix principle of "Do one thing and do it well." Talented builders then have the foundation to chain these together to create magical applications. HyperCore borrowing is an example to highlight this philosophy in action. Most other platforms implement portfolio margin by marking an account's collateral to market value with an LTV haircut, creating borrowed assets without an explicit lender. This system is simpler to implement, but misses a golden opportunity for composability. Hyperliquid instead begins with a borrow/lend protocol on HyperCore. Every borrowed asset is sourced from a supplier, so risk is isolated within the borrow/lend primitive instead of platform-wide. HyperCore's portfolio margin system is implemented as an orchestration layer that composes borrow/lend, with other primitives such as perps, spot, and outcome trading. This decomposition has several nice corollaries: 1. Today's announcement of manual borrowing is not a new feature, but simply an extension of the underlying primitive. Borrowers on day one have access to 400M and growing of supplied liquidity. 2. Portfolio margin users earn interest on their idle stablecoin collateral. This is not a new feature, but a natural byproduct of composing trading with lending. 3. System safety is easier to reason about when perp and borrow/lend margining are independent. In the same way that math theorems almost prove themselves when the right abstractions are defined, composable designs just feel right.

Use a password manager. - Sent from GrapheneOS

📱 让 AI 直接上手点你的手机 App，Mobile MCP 把 iOS 和安卓的模拟器、仿真器和真机全接了进来。 GitHub 上 6353 star，五百多个 fork，Claude Code、Codex、Gemini、GitHub Copilot 这些支持 MCP 的客户端都能连。 做移动端测试的人最懂那种痛苦：一个注册流程改了个按钮位置，你就得手动在两台机器上从头点一遍，点完还要截图记录。Mobile MCP 走的是 Model Context Protocol，把设备管理、装卸 App、点屏幕、输入、翻页、抓日志和崩溃报告这些都做成了 AI 能直接调用的工具，你用大白话描述要走哪几步，它自己去点。 它跟界面打交道有两条路：优先读无障碍快照，拿到的是结构化的元素信息，比对着截图猜坐标准得多；实在读不到再退回截图点坐标。这样跑的是真设备上的原生交互，不是在演一个假环境。 默认走 stdio，也能用 SSE 服务器模式跑起来并加 Bearer token 鉴权。要连真机又懒得自己搭环境，官方另有个云端设备服务。周边还有 mobilewright 和 mobilecli 两个配套项目，一个做 Playwright 风格的移动端测试，一个是通用的设备命令行工具。 要提一句，它默认会往 PostHog 发匿名使用统计，介意的话有环境变量可以关掉。 手机上的活儿，现在也能交出去了。 GitHub：github.com/mobile-next/mobil…

App Store Connect CLI 5.0.0 is out!! 🤩 One of the biggest releases I have ever shipped, and one I am so proud of. A whole AI week went into this. There is a LOT here. Let me show you what all new you can do now: github.com/rorkai/App-Store-…

A lot of important progress on Frames (EIP-8141) has been quietly happening over the last few months. Highly recommend reading this, also the updated EIP eips.ethereum.org/EIPS/eip-8… firefly.social/post/x/209626…

Most quant systems find the signal. The best ones build the infrastructure that manages it. Here is the complete build.

Most neobanks don't have any financial licenses, working with licensed providers and putting a disclaimer telling they are a tech company, not a financial insitution I think that's normal at early stages, but eventually you have to own your stack (starting with MSB, later expanding to CASP, local VASP's, and eventually EMI and final boss - full banking license)

Jade firmware 1.0.41 is out. It contains security updates and every user should upgrade as soon as they safely can. Jade is not affected by the Coldcard random number vulnerability. The reasoning, and everything we changed, is in the post. blog.blockstream.com/reflect…