HN user

mac-monet

25 karma
Posts0
Comments19
View on HN
No posts found.
Understanding ECDSA 8 months ago

Great talk. Wish the camera focused on the slides more.

The ed25519 issues are absolutely insane. Anywhere I can read more about that?

Understanding ECDSA 8 months ago

Was nodding along as I was reading this. I recently was given a paper and spoke with the engineer implementing it. The paper was incredibly dense and hard to parse. But through talking with the engineer and rewriting some terms to more common names, the math turned out to be quite simple. Echoing your sentiment, I wish more mathematicians would use simple terminology. My personal theory as to why this isn't done is the same reason why overengineering happens, that the writer is trying to cover every base but makes the hottest path a jumbled mess.

Gemini is the only plan I have not replaced. Claude and ChatGPT I will switch to depending on the ability of the coding agent, but Gemini is still my favorite for general information and especially for writing assistance.

I have recently been using Zed much more than cursor. However, the autocomplete is literally the only thing missing, and when dealing with refactors or code with tons of boilerplate, its just unbeatable. Eagerly awaiting a better autocomplete model and I can finally ditch Cursor.

Wow these would have saved my team and I a ton of time. Thanks for the links.

For what's missing from the TUI. The fact that the outputs in the main window are not selectable makes it difficult to keep the fuzzer running but copy the call sequence. I have to ctrl+c to get it into my terminal output and copy from there. I think these tools might help here though.

Started using this recently, extremely impressed with this tool's capabilities. The only issue is the TUI is absolutely miserable to use.

One of the biggest pain points for debugging failures that Echidna finds is the path of getting the failure into a forge test that I can replay, and then slowly diagnosing where the bug is stemming from. An alternative path that could be useful is to stream the function call sequence (with the option to disable traces as well) to a file. This would allow easily creating a forge test from it. This file could even be used to generate a test and be diagnosed by a coding agent. Resolving the "last mile" of finding these failures would make the DX absolutely top tier.

Jujutsu and Radicle 11 months ago

For clarity, I actually hate submodules and badly they're implemented. But its what I have to work with!

Since this is adjacent to crypto, I came in here expecting some kind of hateful things being said about it, but seems like a fairly productive and honest discussion, something that is usually lost as soon as the c-word is mentioned.

Despite all of the issues that are within the crypto world, I do think stablecoins are a fantastic use-case that most of us should be able to get behind to break this duopoly. With some oversight/proofs of solvency for the issuers, I hope they can become the dominant payment method. I can say from experience, the fact that I can easily pay friends and also receive yield on my holdings is such a nice experience, especially considering the inflationary environment we're in currently.

A bit off-topic, but the point on duplicate detection reminded me of a thought I've had while taking photos on trips, in a swarm of other people doing the same. I've always wondered how much of the ICloud's storage is taken up by duplicate photos across everyone's phones. How many petabyte would this be? Imagine swapping one person out for another, in the same exact location in an image. How many then?