Thread - Nostr Hypermedia

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. @npub1wmr3...g240 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. @Sirius 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

GitHub

GitHub - damus-io/damus: iOS nostr client

iOS nostr client. Contribute to damus-io/damus development by creating an account on GitHub.

↑ Parent

Replies (3)

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ me@mleku.dev 2 years ago

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...

Ostrich McAwesome 2 years ago

1) Once you have an account established and are following people it is mostly fine, but it's hard to browse the global feed without seeing strongly undesirable content such as lolicon (or worse). This is a natural consequence of being censorship-resistant, but it will scare new users away. I'm excited to see how this can be reigned in without harming the free speech of other users. 2) By "centralized development", I just mean any standard unifying practice for development. Centralizing a core Nostr codebase under GPL would keep it property of the people forever, while making sure all bugs and weaknesses are patched for everyone. Everyone doing things their own way is a recipe for disaster. Death by a thousand cuts. 3) I have never used Damus, so nothing I've uncovered is specific to them. Finding a weakness in Nostr means every affected Nostr project needs to fix it independently. Even I don't want to write that many bug tickets.

2 replies ↓

elsat elsat@habla.news 2 years ago

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.