tigereyeTO
Joined 14 years ago
Joined 14 years ago
Seller and buyer protection don’t exist with cash either my dude.
If you’re going to compare apples and stones at least do it honestly.
Each payment option has its own advantages and disadvantages, and it’s fantastic that we have the freedom to choose from a variety of products and services to use.
I hated it when PayPal froze my funds and wished there was an option where a middleman couldn’t decide who I am allowed to pay. Then Bitcoin came along. For me, Bitcoin works great. For you, your method of choice works great and I’m happy for you.
Ah yes let’s ignore the tons of energy being used in giant data centers run by visa and Mastercard to operate the payment cards used by billions of people around the world.
“Yeah no.”
You know what happened in USA? A lot of people got their cash stolen.
Your arguments are as coherent as the dissonant “Yeah no.”
Bitcoin addresses encode the ripemd160 hash of the public key, so by default when payments are made to new addresses they are not quantum crackable.
But when someone spends from an address they publish the public key to the chain as part of the spend. From then on, any new deposits sent to the same address are at risk of quantum attack
So it’s not enough to say “we have 5Ghz wifi here so it’s fine” because there are many channels within that band which may not all be treated equally.
Canada also participates in trade, is located in the same geographic continent, and is also suffering housing issues.
I too struggled to identify which “our” the comment referred to
Your imaginary dog can’t teleport value across the globe instantly, but Bitcoin can.
Yep, checks out.
The very early days of Bitcoin had addresses created using the now-deprecated P2PK address variant—Pay To Public Key. These addresses are simple encoded secp256k1 public keys with no hashing.
There are still > 1.5 million BTC stored in P2PK UTXOs as of this post, all of which are up for grabs to the first person who can derive the private keys for the known public keys
My gripe with passkeys is they are almost always implemented without a second factor.
You’ve mentioned the rare case of 2FA with a passkey as being a bad thing, but in my opinion those few cases are actually doing it RIGHT.
With passwords and 2FA, if someone manages to copy your primary authenticator (password) they will still be locked out because they don’t have your secondary authenticator. This protects you against malware that steals your password database.
But the way most companies implement passkeys (single auth), if someone steals your passkey database they can use it immediately. For all of the true measurable benefits that passkeys bring (not memorizable, higher entropy, automatic storage and use in a database) they are almost always used in a way that has this huge drawback: no 2FA.
This is not an issue with passkeys directly, it’s an issue with how services implement passkeys.