eamann

6 ms·

1.
Rebuilding a Dead iPod Game(eric.mann.blog)
2 points by eamann 9d ago|0 comments
2.
Show HN: Ext-Infer – Native LLM Inference and Embeddings for PHP(infer.displace.tech)
2 points by eamann 3mo ago|0 comments
3.
Canton vs. Public Crypto: A Technical Comparison(eric.mann.blog)
3 points by eamann 5mo ago|0 comments
4.
What is Canton Network (and why should you care)?(eric.mann.blog)
2 points by eamann 5mo ago|0 comments
5.
The 0.25% Background: Building a Rarity System into a Portfolio Site(eric.mann.blog)
2 points by eamann 5mo ago|0 comments
6.
Buy Them the Tools(eric.mann.blog)
4 points by eamann 6mo ago|0 comments
7.
The Agentic Harness Problem: AI Agents Need Better Guardrails(eric.mann.blog)
2 points by eamann 6mo ago|1 comments
8.
by eamann 6mo ago
It's to protect against the whims of a small set of people. If one person holds the signing key to do something critical in your system, they're both a single point of failure and a huge security risk all in one. If you distribute
9.
by eamann 6mo ago
Oblivious transfer - party A creates two random values (x_0 and x_1) and sends them _both_ to party B. Party B picks one and uses that to compute future values that are sent back to party A _but without telling party A which of the two valu
10.
by eamann 6mo ago
You're correct there that proper use means even the owner can't access it. But in a single key scenario they can still act unilaterally. The advantage of TSS is the removal of that level of unilateral action.
11.
Watch Cryptography Happen: A Terminal Animation for Threshold Signatures(eric.mann.blog)
2 points by eamann 6mo ago|0 comments
12.
Why One Key Shouldn't Rule Them All: Threshold Signatures for the Rest of Us(eric.mann.blog)
17 points by eamann 6mo ago|22 comments
13.
Show HN: DKLS23 2-of-2 threshold ECDSA signature ceremony visualized(github.com)
1 points by eamann 6mo ago|0 comments
14.
The Upfront Investment That Saves 10k Hours(eric.mann.blog)
1 points by eamann 6mo ago|0 comments
15.
From Defense AI Drift to Policy Enforcement: Why I Built Firebreak(eric.mann.blog)
2 points by eamann 7mo ago|0 comments
16.
The Gravity Problem: Why Defense AI Companies Drift Toward Offense(eric.mann.blog)
1 points by eamann 7mo ago|0 comments
17.
Split – The Coin of Fate(split.displace.tech)
2 points by eamann 8mo ago|0 comments
18.
I built a Kubernetes deployment tool(eric.mann.blog)
2 points by eamann 8mo ago|0 comments
19.
by eamann 8mo ago
I like this take-home approach. Usually, I've been against that kind of outside work but in rare cases (i.e. leadership positions) have assigned take-home case study style presentation work to gauge communication skills. For engineers,
20.
Short Stints, Real Experience: Rethinking Career Tenure(eric.mann.blog)
3 points by eamann 8mo ago|1 comments
21.
When It Rains Planning for AWS/Cloud Outages(eric.mann.blog)
2 points by eamann 11mo ago|0 comments
22.
Your Return-to-Office Policy Is Killing Your AI Strategy(eric.mann.blog)
2 points by eamann 1y ago|0 comments
23.
WordPress Infrastructure in 2025: Time for a Modern Approach(eric.mann.blog)
1 points by eamann 1y ago|0 comments
24.
by eamann 1y ago
Sure, your experience sucked. But by all means let's continue to look down our noses at a programming language based on mistakes made 20 years ago.
25.
Signal vs. Noise: How AI Slop Kills Conversation(eric.mann.blog)
4 points by eamann 1y ago|1 comments
26.
Distilling the Cloud: The Journey Continues(eric.mann.blog)
1 points by eamann 1y ago|0 comments
27.
Building Scalable Systems While Paying the Bills(eric.mann.blog)
1 points by eamann 1y ago|0 comments
28.
The Deceptive Promise of AI(eric.mann.blog)
2 points by eamann 1y ago|0 comments
29.
Goodbye WordPress: A Eulogy(robertdevore.com)
5 points by eamann 1y ago|0 comments
30.
by eamann 1y ago
It's a bit disappointing that a seemingly official project isn't using commit signing for verification and non-repudiation. It's open source, great! But it's also pretty massive (i.e. hard to review everything) and the c

More ›