ec
kpr797
ec003d5ee5101019f1bb8c586e9654adba913efc16f02051c39758694f70becd
Replying to Avatar jb55

#foodstr

You eat better than 90% of people, sir.

Technical debt is any work that necessitates additional future work that could have been avoided.

It's easy to say "it's not technical debt because it was so effortless to implement", but that is a very dangerous lie.

Creating technical debt is extremely easy to do.

Then cookies should be broken until the website requests permission from the browser to use cookies, and the browser itself should be the one responsible for displaying the simple "accept all” and "reject all" interface.

An anology would be like how an iOS app cannot see your physical GPS location without first being granted permission by the user. Cookies need to be access restricted in a similar fashion.

If baffles me how many "smart developers" don't understand this.

How much do you currently weigh? How long have you been at it so far? What is your ideal target weight? Do you enjoy the exercise and foods you're currently doing?

It is actually quite sensible to have it be as easy to opt-out as it is to consent. Other wise any consent that is obtained is meaningless, because most people will use the consent button as a "just let me see the content" button, rightfully annoyed and deterred by the hoops they would be forced to jump through by clicking anything else.

I think we're going to see this happen a lot in the lightning network provider space too.

How much funds were lost on #coinos these past weeks? Was it all recovered?

Replying to Avatar waxwing

I get the impression Saylor is not aware that ZK proof of assets/reserves exists already; for example both an implementation of the basic idea (clunky and rough around the edges, but still) in my https://github.com/AdamISZ/aut-ct/tree/master/auditor-docs based on curve trees + bulletproofs and halseth's output-zero: https://github.com/halseth/output-zero which doesn't directly do this job but has the machinery to do it (and hooks interestingly into utreexo btw). Liabilities proofs are different but existing ZK techniques already help there. The science basically already exists.

(Note: here I mean cryptoccy liabilities, i.e. user account balances; the whole fiat side is separate)

I don't think companies should be doing what Binance does, posting an Excel spreadsheet with all of their addresses exposed to the public. It's security 101 that this kind of privacy and metadata leak is an attack surface, no matter which way you slice it. We have the technology!

nostr:nevent1qqsg5vlqalth0h2dn8zz4mxf96z6trzxthrat4lvm5phg28u4pvtffspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgs8efndg9ntzm65595xsxgm58rrs65hvcj0gc608ztdndn5pgugegcrqsqqqqqp8jmgzt

Zero knowledge proofs have a tendency of confusing the shit out of most people.

Accounts get compromised all around the world, all the time. If it's just one of your many accounts, the damage is limited. But if it's your one and only nsec, and you use it all over the place, that's going to suck, a lot.