I'm looking for a nostr list event editor webapplication.
It should be able to create a 30000 profile list with simple UI, showing the profiles. Then show me the event's naddr. No more, free of bugs.
#asknostr
I hear cashu here and there, everywhere, all the time.
And yet, nobody mentioned V2, a braking change that suddenly broke all nonactive cashu projects.
I might be wrong and just have missed some posts, but still... The following conclusion of mine comes from many such situations:
Are we in the mud of honey? This is one of the mistakes a community can make: being overpolite and focusing only on the good, because nobody wants to take the risk of reputation degrade by mentioning annoyances publicly about anything related to bitcoin.
This is inherently a problem of a society of individuals. This is why we need proper communities on nostr (and not just community software, we have enough of that).
Up for a debate. Change my mind.
I love that I can just clone git repos intuitively, using this command:
`git clone nostr://dan@gitworkshop.dev/ngit`
I know who the developer is (and his nip5), I know the project name, the rest is automatically filled in. I love that I don't have to copy/paste any nevent or naddr.
This is still my favourite feature of ngit.
https://opensats.org/static/images/projects/ngit.svg
Communities are by nature socially centralized. Therefore the right design in my opinion is to have its content bound to pubkeys rather than server addresses. The data can still be redundant if community members take care about archival and hosting.
For public communities - like opensource development - this is definitely the way and the data should be widely replicated.
This is a key property of #communikeys.
My humble opinion about privacy is: if you need personally, generate a new pubkey for the kind of interaction you want to be hiding.
View quoted note →