Is there an official list of standards that one must meet to earn the right to have an opinion on Nostr development and practice?
I currently spend time testing and reporting issues as I find them (admittedly, I do need to get better at doing this using repo reporting tools in ways that developers prefer). I'm educating others about the benefits of Nostr and related tools as often as I can. I donate what I can monthly or purchase products from developers to support them financially. I'm studying computer science and related topics to contribute in ways I'm interested in. I buy books and build things like SeedSigner (npub17ty…3mgl) to give them to people who want to learn about securing their assets.
What am I missing? Contributing code? If so, how much? What must we users do to matter or not be offensive? What must I do to never irritate developers? Think the same? Ignore what I see as potential problems and never speak of them? Communicate in a specific way? Never make mistakes?
Please just give me a list and I will at least know where I stand and what I must do. Tell me exactly where I'm going wrong and how exactly I can fix it. I genuinely want to know the exact standards I have to meet to matter as much as developers.
I can't figure it out. Maybe I am the problem, but I can't fix a problem without knowing what the problem is.
IS there a standard that will please every developer? Most? Some? One?
I'm frustrated as a user, tester, supporter, and someone who wants to see Nostr succeed. Some developers seem to be frustrated by people like me. What should we change?
matt / Matt Warren⚡Not Related to Elizabeth Warren
npub1l6…uj5rc
2024-08-27 13:39:49
Author Public Key
npub1l6scds4yv7xmcsmhqnhdy9sggm520q09lvts2m5mkvecgr2mmmeqsuj5rcPublished at
2024-08-27 13:39:49Event JSON
{
"id": "519c39301e9ef99cb964000bb041e8bfe2a9b6bd2b626ce67632c538a804538e",
"pubkey": "fea186c2a4678dbc437704eed2160846e8a781e5fb17056e9bb333840d5bdef2",
"created_at": 1724765989,
"kind": 1,
"tags": [
[
"p",
"f2c96c97f6419a538f84cf3fa72e2194605e1848096e6e5170cce5b76799d400",
"",
"mention"
]
],
"content": "Is there an official list of standards that one must meet to earn the right to have an opinion on Nostr development and practice?\n\nI currently spend time testing and reporting issues as I find them (admittedly, I do need to get better at doing this using repo reporting tools in ways that developers prefer). I'm educating others about the benefits of Nostr and related tools as often as I can. I donate what I can monthly or purchase products from developers to support them financially. I'm studying computer science and related topics to contribute in ways I'm interested in. I buy books and build things like nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl to give them to people who want to learn about securing their assets.\n\nWhat am I missing? Contributing code? If so, how much? What must we users do to matter or not be offensive? What must I do to never irritate developers? Think the same? Ignore what I see as potential problems and never speak of them? Communicate in a specific way? Never make mistakes?\n\nPlease just give me a list and I will at least know where I stand and what I must do. Tell me exactly where I'm going wrong and how exactly I can fix it. I genuinely want to know the exact standards I have to meet to matter as much as developers.\n\nI can't figure it out. Maybe I am the problem, but I can't fix a problem without knowing what the problem is.\n\nIS there a standard that will please every developer? Most? Some? One?\n\nI'm frustrated as a user, tester, supporter, and someone who wants to see Nostr succeed. Some developers seem to be frustrated by people like me. What should we change?",
"sig": "a32cbee1e421734ec863667c3a9280f5f0cf84c076a1da083db73c8df78876b16e147763165bf1d5ec40d7a5b72cc977827974d53d7dd8b94c79bab07957bcec"
}