Other peeve: quote the core of the bug report you're closing, so when GitHub inevitably goes away/turns evil/starts charging, you don't lose half your knowledge. The git tree should always stand alone.
1,432 karma · joined May 20, 2011
Other peeve: quote the core of the bug report you're closing, so when GitHub inevitably goes away/turns evil/starts charging, you don't lose half your knowledge. The git tree should always stand alone.
For most protocols there's only reading and writing, so you can use odd bits to mean "backwards compatible features, you can read even if you don't understand" and even for "stop, we broke compat".
Still, Open Timestamps does exactly this, and had been running for over 8 years now.
Employment-at-will takes some cultural adjustment, too. But for tech folks tends to be a net win. You just need to set your expectations accordingly!
Hope you have a great day!
He's repeatedly denied it, and your ignorant claim can only bring him and his family trouble.
(Also, I've known Adam for a number of years through multiple Bitcoin conversations and I can personally vouch that it's not him!)
But if you're trying to build something for decades, as you should be for internet infrastructure, there isn't much option.
Curiously, this energy hunger is driving decentralization despite the otherwise inevitable benefits of scale.
Heres the inline:
See https://github.com/rustyrussell/runes for a simpler alternative and implementation (this has C and Python, but there's also a Rust implementation because why not?)
However, the "no db access" property has proven to be untenable in practice. Users end up wanting to see what runes are issued, blacklist them, know when they were last used, and have rate limits. The last two are a killer, requiring some state to be kept (unless your system allows you to return a modified rune to the user, which is a different workflow from normal bearer creds).
Because payments happen been pairs, there's no easy count of activity. The best estimates I know of are things like https://blog.river.com/the-lightning-network-in-2023/ which is almost 12 months old.
As to "no wallets support it", that's a strange thing to say, since lightning wallets support it, obviously.
I'm yet to see any comparable statistics in L2s on Ethereum? Was hoping you'd have something there, too :(
You can rate-limit (runes do this, which are simplified macaroons) but then the server is no longer stateless. Pretty sure I've ranted about this in HN comments before, could dig it out if you're interested?
Having created a micropayment network, you quickly discover that infrastructure does not exist where you want to use it. Web APIs are kind of the obvious use case, but because there was no micropayment system they trended to an account and batch payment method by necessity.
This aims to fill that infrastructure gap. Of course, there's a huge chicken-and-egg bootstrap problem, but you have to start somewhere!
This is legal. But dereferencing old_pointer even after this check had passed is undefined.
https://www.theonion.com/the-onion-looks-back-at-the-sound-o...
It's hard to imagine a deflationary world where bosses had to negotiate with workers to reduce their salary annually, which kind of shows how powerful this idea is...
He's repeatedly denied it, and your ignorant claim can only bring him and his family trouble.
(Also, I've known Adam for a number of years and I can personally vouch that it's not him!)