Although it is the first time that I have access to this document, it feels familiar because Claude embodies it so well. And it has for a long time. LLMs are one of the most interesting things humans have created. I'm very proud to have written high-quality open source code that likely helped train it.
For me, Hetzner, Starlink, and Tailscale are 2014-era startups: stellar products that turn you into a zealous militant for the companies. This is a very exciting development. I am very much looking forward to their dedicated offering extending to the US.
Ethereum has different client software, they must all use the same consensus rules: produce/gossip/accept transactions and blocks that follow a certain format and respect certain invariants. When that specification is updated, a hard-fork occurs. It's not a problem if all clients meet the new spec perfectly but sometimes bug happens and different clients disagree on what constitutes the canon chain. This is what happened here: the OpenEthereum client (11% of the network) has had a bug following the Berlin hard-fork (network upgrade). Nodes runnning this client are stalling at a certain block because they don't recognize the new "post-Berlin" blocks as legitimate because of a bug in the implementation.
>But virtually all money is being made on being a broker for people speculating on Bitcoin as if they're buying gold, with no significant intent to use bitcoin.
You have to wrap your head around the idea that the main way to use a store-of-value is simply by holding it. Holding is using!
Short description: RAI dampens volatility (goes up slower, goes down slower) of its collateral (Eth). All thanks to some straightforward control theory tricks!
You can inflate the money supply and still be "deflationary" if the convenience yield of holding the money (tokens, UTXOs, or whatnot) exceeds or neutralize that inflation rate. You make an excellent point, Bitcoin doesn't have to overtake gold or become a global-reserve to change the world. It just has to be a plausible alternative that enables people to opt-in or out of the system. It has largely already achieved that and I'm hopeful for a future of monetary pluralism.
That's a really good point, this settlement is extremely favorable to Tether and Bitfinex. It's odd to see people persist in pinning Bitcoin's market performance on Tether issuance after reading this settlement from NYAG. Chunks of Tether collateral weren't fully liquid but my takeaway is that they operated on a genuine best-effort basis. As another comment put it, Tether definitely operated in a grey area legally - they hacked the system, but they're not the fraudsters some media, comments, or rumors made them out to be.
Fashion is hardly an industry where it is easy to achieve fame or success, let alone "immortal" notoriety like Lagerfeld or Cardin. However, it is true that countries with a lot of luxury fashion houses are more likely to consider fashion as a proper art form than not. That's an important distinction from software. Successful designers are artists and that accounts for something in the way their legacy is celebrated.
A couple years ago I attend this talk by Paul Wesling at Stanford. It's the most interesting, exhaustive account I have heard. It goes all the way back to the early days of Ham Radio enthusiasm in the Bay Area around the early 1910s, following the stories of three pioneers: Jack McCullough, William Eitel, and Charles Litton to modern days.
>There's a lesson in all this: have one joint and keep it well oiled.
>Protocol designers underestimate how badly people will implement their designs. Writing down how you think it should work and hoping that it'll work, doesn't work. TLS's protocol negotiation is trivial and the specification is clear, yet it still didn't work in practice because it's difficult to oil.
>Rather one needs to minimise complexity, concentrate all extensibility in a single place and actively defend it. An active defense can take many forms: fuzzing the extensibility system in test suites and compliance testing is good. You might want to define and implement dummy extensions once a year or such, and retire old ones on a similar schedule. When extensions contain lists of values, define a range of values that clients insert at random. In short, be creative otherwise you'll find that bug rust will quickly settle in.
The table is correct. First because design intent is irrelevant. Second because the author clearly states that the focus of his comparative study is on *-preimage resistance vs collision. There is more to the article than the table :)
I was writing this exact comment. That article and title are in very poor taste, and hold zero intellectual value. That’s a tragic and morbid coincidence. The subtext of this piece along with the timing of this post are disgusting.