dgrove

Joined 12 years ago

Karma
441
Submissions
63
Member since
Dec 1
my public key: https://keybase.io/drgrove; my proof: https://keybase.io/drgrove/sigs/7vNTktyLv2POAACx2FJXZP2H_CuAyrmGv17wvdW9DLk openpgp4fpr:c92fe5a3fbd58dd3ec5aa26bb10116b8193f2dbd
View on Hacker News

Recent submissions

Comment · 9 months ago
I'm not sure what problem this is solving. This seems like chainguard but being built in "your ci" (github) vs "their ci". Images may be a bit smaller, but this is already a feature set that wolfi already allows for. Besides that chainguard is not full-source bootstrapped.
Comment · 1 year ago
Also login over a VPN unless you want your IP leaked to everyone else
Comment · 1 year ago
Just because you make exceptions doesn't mean everyone else does
Comment · 1 year ago
Comment · 2 years ago
Comment · 2 years ago
scp has the assumption that you have a login on the computers you're trying to share data from. wormhole allows for sharing with others without providing login access to the computer
Comment · 3 years ago
Comment · 3 years ago
The lack of package signing and reproducible builds leaves a lot to be desired
Comment · 3 years ago
HKPK doesn't have a ton of adoption and only works in browsers. So this does nothing for curl, wget, pip
Comment · 4 years ago
Sure, so you add it as part of the P2MS script but that doesn't solve the issue of every re-key costing money
Comment · 4 years ago
Is this because you have a time-locked transaction to move the funds from the P2MS to a P2PKH? How does that work when it's "re-keyed"? Wouldn't each re-key move to a new P2MS and have a transaction fee associated with it as well as have a second transaction for the HTLC transaction?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton