Do you cut the vanilla beans lengthwise, or just leave them whole?
That’s too hard for most people too.
We need to decentralize and proliferate private relays. And the clients need to be much better at managing them.
I think Discord, for all its faults, has this pretty well wired.
Okay, there’s “global” and then there’s my feed of all my follows. There would have to be additional “local” feeds, and when posting to that local feed, it only sends to that one relay.
There also needs to be a way to refrain from broadcasting private relays onto my recommended relays.
What if people could host and monetize their own community on #Nostr, using NIP05 domains as a way to identify community members? They could enjoy a local content feed of like-minded people while remaining connected to the rest of the network...
I feel like this could be really powerful...
👀 nostr:npub10qdp2fc9ta6vraczxrcs8prqnv69fru2k6s2dj48gqjcylulmtjsg9arpj
How would client UX separate the private community with the rest of nostr?
It would be awesome if Blossom would provide that info in the response header. That way apps could make an http request for just the header without downloading the whole thing.
Why does the path need a “.ext”? The sha256 should be enough, right? Why confuse things with whether it’s a jpg, pdf, gif, etc as part of the path?
Anyone feel like making an ostirch pic. 1K sats for the best one based on - NOSTRATU
https://en.wikipedia.org/wiki/Nosferatu
Hey remember 'The Game'. I think we could make a good horror movie out of this nostr:npub17ranr5vpp20etheaz78u6e72pvyc0xk3r6rgnetfvtxc88acat2q4nhenz #horror #horrorstr
Dammit! I lost the game.
He’s not against the Ukraine Russia war, he’s just pro-Russia. And he can’t wait to watch his bosom-buddy Putin get what he wants.
Also, it’s possible that (far) in the future, computing power gets sufficiently advanced to break private keys. The network would move to a new cryptography scheme at the first hint it was possible, but “lost” coins wouldn’t be moved, and would end up being “salvaged”.
Much like much like a 1600s sunk pirate ship filled with gold. That gold was likewise “lost”, but now we have the technology (submarines) to retrieve it.
I’d be more than happy to keep the lines of communication open. I have a pretty unique use-case, and if you’re into it, I’d love to tell you more about it. In fact, my hope and dream is that my “unique” use-case is the solution to the monetization of relays that has always been a problem for Nostr.
Chorus looks awesome. Thanks!
And thank you, nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c !
I've been working on a nip42 auth proxy for strfry (Or any relay). I tricked it out for working with the relay tools API and multiple subdomains, but it can easily work with a static auth list or something like that with some modifications. It's working pretty well so far and live as a feature for any relay.tools relays. Example at auth.nostr1.com https://github.com/relaytools/interceptor
There's also fiatjaf's khatru, natively supports nip42:
https://github.com/fiatjaf/khatru
@mleku is also working on a heavily modified khatru for performance called replicatr I think he is releasing it soonish..
That’s cool! There is an issue for NIP-42 implementation in strfry, but there hasn’t been a bunch of work on it:
https://github.com/hoytech/strfry/issues/47
nostr:npub19mc0en74540rd0ytuwjjtswwjleqa2a2jnnfmqh7hltyrk2gps6skpz875 was going to work on it, but I haven’t heard from him in a few months.
Are there any really performant #nostr relay implementations that are still being developed?
I’m expecting thousands or even tens of thousands of simultaneous connections. And I really need NIP-42.
Strfry hasn’t been updated in 5 months. And it doesn’t support NIP-42.
Nostream is definitely popular, but I worry about the performance. And it doesn’t support NIP-42 either.
Maybe nostr-rs-relay?
#asknostr
It’s my favorite nerd-joke of all time.
The two hard problems in Computer Science:
2. Cache Invalidation
1. Naming things
0. Off-by-1 errors