please stop saying "submit PRs to x" everyone
the devs are usually either too busy or too obnoxious to pay attention to such efforts
just fork it and fix it on your fork, maybe they might consider backporting it later from your fork...
Thanks for bringing privacy to the forefront. Few read the respective nostr github project documentation on privacy. Your method of exposing privacy on base nostr protocol has been effective.
> hardly any moderation tools
Despite this, the discourse is more civil than that of twtr. Maybe it’s a function of nostr’s tiny size, and lack of algos.
nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 and nos social are as far as I’m aware thinking and developing most on moderation tools.
I don’t know how far they’ve gotten - that said one of the benefits of nostr is you don’t have a mandatory moderation curator in a WEF stooge. You can have a feature where you choose your own moderator - for instance you can choose Jack.
nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk implemented web of trust network hops filter more than half a year ago on Iris messenger.
> no centralized development
Yes, this is a feature. Otherwise we’ll get another closed big tech gulag.
You are more than welcome to submit PRs to Damus, and I’m sure many others will happily review patches. Nearly all of nostr is FOSS, and lead devs welcome patches.
Example code and issues https://github.com/damus-io/damus
Discussion
Having a front row seat to nostr dev it’s worked quite well for Damus.
Lead devs appreciate clear, and succinct patches that do a single thing well. These are worth their weight in gold. There are sats reward if done correctly at least from Damus.
Is there friction in establishing contribution norms and the first patch- absolutely. Veteran devs figure it out quicker than junior devs .
Not sure the OP’s track record with FOSS - maybe he needs a prompt.