Are the technical details of how this display works public? A patent perhaps?
I imagine it _works_ but doesn't scale
Happy Canada Day! 🍁
Sounds like a feature
You can hardcode a large list and only 1 need be honest & operational for your client to find more honest peers.
If 99 of 100 hardcoded peers are down, you're still good. And on the next client update you change the hardcoded list to another working set of 100
Finding seed nodes is a much bigger problem than nostr, even bitcoin has hardcoded domains for finding the first peer.
In practice I don't think this is actually a big issue
There's a lot of reverse proxy infrastructure that won't like this. Would be wonderful if we could at least put the original naddr in a header or something
Which client supports nip-95?
I like blossom's approach. https://github.com/hzrd149/blossom/blob/user-server-list/buds/03.md
Could do the same with nip96.
IPFS would work as well but I prefer http unless the file is extremely popular
Nice job, what is your rating?
Pretty neat that there's no MEV, though it looks like it has the same high liquidity requirements of Ark
nostr:npub1da72xwy4h4727jyqmcxw8dzhzyq8ghr634csuze4gyhnu2guv5uqm3ez52 is working a Logseq type of application for interoperating with relays.
I wonder what kind of a headache that must be.
I also wonder if the honorable nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc has used Logseq 🤔
Blastr style storage is what attracted me to build on nostr in the first place. I'm not prescribing it, but the option for the user to choose a Blastr proxy relay is great
Are you going to open a nip? Or is your goal to just raise awareness of your tool and hope others carry the flag for a nostr integration?
If urgent (it rarely is), push notification. Otherwise email.
What's your favourite tool to grab the raw json of a nostr event given an ID?
How so?
Damus does not add PoW to your posts. That's true for basically all notes on nostr right now. There's not really much point adding it since no apps/relays use PoW based spam filtering
You can already do this attack with a 2 of 2 multisig where one party is the government. You need their permission every time you transact, and will only approve transfers to another 2 of 2.
For apple, the enclave requires a faceID proof before it'll sign. But, afaik no btc wallets use them because the curve the enclave supports is secp256r1 (whereas bitcoin is k1).
I heard op_cat provides enough account abstraction to make it work, but, have not looked into if that's true or not.
Right I see the use to compensate for the lack of a built-in secure enclave (like most PCs), so it can't be high jacked from working memory by other malicious software 👍