The whole point of a hardware key is that you cannot extract the private keys. Since when does Yubico allow you to do that?
1. No (although they might be able to add support for it if they wanted to)
2. It's not a perfect fit, because you don't want to lose your Nostr identity when you lose or break your Yubikey
Perfect use case for anon VPSs!
I had this on CD once. So good.
*opens nicotine+*
I get the same error.
This is rather crude, but I'm using it to back up all of my Nostr media uploads for now (until Kosmos storage has NIP-96 or Blossom support):
https://storage.kosmos.org/raucao/public/shares/241102-2154-download-images.txt
Can be used like this for example:
`./download-images.sh ws://localhost:7777 $pubkey_hex ~/backup/nostr/images/`
(It will create a subdirectory per pubkey in backup dir. Needs nak and jq installed.)
There's clearly a Strudel in the logo of noStrudel. This is lies!
Terrible channel partners. Here's another 5M sats inbound...
https://mempool.space/tx/826fec7c1bc19dd37971a81e1d264f489707d9936e992a801eae1ae0282cb581
What's the cryptic secrecy for? Why not build in the open? 🤔
Sounds like a problem with Coldcard UX, not hardware wallets in general.
Set up strfry on my laptop, with a systemd timer to regularly sync notes from my home relay via negentropy. So smooth.
presumably relays would take on the role of breaking down nostr into smaller, overlapping communities, but nostr is so small that relays are basically interchangeable. what we can do today to facilitate this is develop client side algorithms like this one: https://nostr.thecaptain.dev
An algorithm can't find content for you if it doesn't know you. And it cannot know you if you're a new user who just created a key pair.
presumably relays would take on the role of breaking down nostr into smaller, overlapping communities, but nostr is so small that relays are basically interchangeable. what we can do today to facilitate this is develop client side algorithms like this one: https://nostr.thecaptain.dev
When I open that I just get an infinite spinner, and from the network panel I can see it's not using my relay list...
You could only verify that a result has been produced by a certain key, but not how many results it has produced from which the published one has been picked.
They're all buggy, but noStrudel works best for me.
The problem with a network this small is that, to a certain degree, the network is close to being just one large community, instead of many overlapping smaller communities. With federated systems it's more obvious that the people you might strongly disagree with come from different domains, which just also happen to be able to communicate with yours. But I think a network without this required affiliation needs a certain minimum size to become home to a truly diverse set of people.
I think both community-focused software as well as non-social-media use cases are the solutions in the end. If Will can't post stuff like that without it affecting new users, then the entire protocol is DOA, isn't it?
It's beyond me why Zcash is not regarded as a complete shitcoin. Here's the first reason Zooko states for why Zcash will switch to Hybrid Proof-of-Stake:
"It reduces supply of ZEC by locking up staked ZEC and increases demand for ZEC by giving people something else to do with it."
Not enough demand for "money"? People have no idea what to do with their "money"? Let's lock it up and reward investors with dividends!
Now imagine someone looking at this chart, even adding it to their own blog post, and then linking said post with the comment "Zcash is winning":
Am I thinking about this the wrong way perhaps? What am I missing about this amazing currency?
I can't help but think that the Satoshi press conference is some kind of Banksy prank. Either way, it's certainly a good method for guaranteeing a full house.
few understand we have one of the best protocols for efficiently syncing datasets between nostr nodes. nostr officially grows up when NIP-77 lands.
Plz update the Damus relay so we can sync with strfry 1.0? 🥺
