throwaway92394

Don't get me wrong I do too. I'd prefer it if everything just used USB C.

I just wanted to point out that it's not universally superior to micro USB or lightning, and there are places it could be improved.

You run into the same issue you do with 2FA -

I cannot remember my own SSN. What happens if I lose my license, SSN, and master password manager password in a fire? What happens if someone has a stroke and forgets a recent pin code, etc.

Do I go to my state and request new IDs? How do they authenticate me?

So in the US you can do "credit freezes" which prevent people from taking out new loans/new cards in your name.

HOWEVER - you can't do anything about the fact they can call up your bank, say "I forgot my password" and then give them your SSN. Your bank will happily reset the password for them. If someone has your SSN they essentially have everything they need to get access to any of your financial, medical, or utility accounts, and can also use it for KYC/AML to open say a crypto account in your name. You cannot do anything to prevent this option.

But more importantly - can we embed ID3v2 inside ID3v2?

> For the sake of simplicity 2-of-2 multisig that downgrades to 1-of-2 multisig over time should capture the essence of how these notes work. > Users can always claim funds after the expiration date of January 3rd 2029 using the user key stored on the note.

Interesting, thank you. That does seem more reasonable to me. Best of luck with your project.

I'm not defending github specifically, I have no experience with the customer service and have no reason to beleive they are or aren't garbage. I'll assume they are garbage.

To be fair, what do you expect the first representative to do/say? They responded in 3 hours, and it's unlikely they can do much beyond escalate this issue internally. We can't expect them to say "We're going to do sweeping changes" at this point.

Github in the past has done sweeping changes for things such as youtube-dl. They created a large blog post about it, including having both programmers and laywers review every DMCA request, and allowing the most minimal amount of changes to comply, etc. That type of response takes time and coordination.

Even cloudflare with their CEO/CTO can't offer sweeping changes in a HN comment. There's layers to this. You can only really expect damage control from a HN comment.

> We will have a security overview doc up soon, we ran out of time to have it ready today.

I mean this respectfully - why would you release a cryptographic method of transferring money - without going into detail of how it actually works? That's kinda the entire point of cryptocurrency, that we have a way to be mathematically confident the money is safe - but you didn't tell us the math. Especially on HN were a lot of the audience is technical enough to want to and be able to verify it to some degree.

I see you have patent US10896412B2, which honestly I have to ask how this is any different from any other hardware wallet?

> A physical cryptocurrency may comprise a physical medium and an attached processor.

I read some of the details (admittedly not all) and I'm still unsure how this is different from any other hardware wallet. AFAIK this is just a hardware wallet that exposes it's public key, then exposes it's private key when you cut the wire? Then we still need your signature to transfer the crypto, which is so double spend is prevented?

Also, if your servers go down or you're hacked or rm -rf dir/ * happens, will all the notes become unusable? Are we relying on you to maintain servers indefinitely?

> Innovation is overrated. And standardising is not blocking.

Hard disagree? Both lightning and USB C were massive improvements in durability compared to Micro USB - I'd argue lightning is still better in that regard, because there's no thin piece inside the phone that can break (did phone repair, and 99% of the time a "broken" iphone port was just stuck lint).

USB C is not universally better then then Micro, namely it has a much larger footprint both on the connector side and the PCB.

> Will EU block innovation?

So my question is - if there's a new USB standard connector that's smaller, or is inside-out for better durability - is it now prevented from being used?

Or apple's iCloud (see their passkey thing also currently on the front page)

EDIT: Yes you don't need to use a syncing service. But it will be important for it to be portable between syncing services, as that is what most consumers will be using.

Does anyone know how this/FIDO/Webauthn affect privacy? How well supported are alt accounts? Are they easy to tell they're from the same signer?

I figure privacy is fine as long as the implementations allow you to select which account to login with. Is this currently a thing? From everything I read it seems like the current implementations are only meant to support one identity?

EDIT: These are great responses, also curious if anyone is aware if Apple's current implementation supports multiple identities?

> Unfortunately only mobile OSes are on the forefront of this.

I'm not sure why the OS would have to manage this. For example when using electron you can use node's vm and run js in a seperate context. Its a seperate process but doesn't require anything special from the os for it.

mobile OSes do sandbox the entire program usually by default though.

Ubuntu sorta tried to with snapd. Windows tried to with UWP.

Yeah my impression is they're all marketing and care relatively little about privacy. How you can claim to care about privacy but still require an email is beyond me.