Nostr Development lifecycle

- Dev doesn't find something he's looking for and soft announces a project

- crazy guy who follows all projects posts links to 10 projects that are almost it but not entirely

- Dev begins work and showcases a working prototype.

- crazy power users vocally demand features no one else but 5 people need.

- Dev spends hours delivering on nieche features and unveils them.

- no one uses it.

- Dev gets bored and moves on to next project.

- Repeat.

Reply to this note

Please Login to reply.

Discussion

Imo, nostr devs should be tied directly to their local bitcoin meetup or some event or whatever. As a developer myself, developers are retarded when it comes to prioritizing features and products for others. Thats why product and project managers exist.

Please no. The last thing Nostr needs is more dev work tied to Bitcoin meetups, podcasts and stuff for Maxis. That already makes up about 90% of Nostr.

I’d much rather see indie tech enthusiasts building ephemeral software for a handful of other devs than anything that drags Nostr deeper into the BTC Twitter hole. Personally, I value FOSS devs who create software for actual human beings (and who are willing to fix bugs and maintain their projects instead of abandoning them for the next experiment once the hard brownfield reality sets in). We cant have everything of course, and proper product vision is hard. But Nostr needs to start bringing in people from outside the BTC Zeitgeist.

Bitcoin meetups have use cases that apply to a multitude of other groups. Store fronts, forums, media, private comms, calendars, polls, streaming, fundraising, elections, recomendations, etc.

Maybe its just my meetup, but we have lots of needs that arent twitter related that nostr could solve but hasnt.

Fair enough, valid point. I think we need to find more users (and devs) at non-BTC meetups as well. I can help with that; I run a few myself. And now, thanks to Fiatjaf and the great work by nostr:nprofile1qqsvyv8d6dx2tjp33069j2kq2mx7xage6w2upyzvxl4pcegt3t22wyspz9mhxue69uhkummnw3ezuamfdejj7qfqwaehxw309ashqmrpvdjkjmn5dpjhxatw9ehx7um5wgcjucm0d5hszyrhwden5te0dehhxarj9ekk7mf00fytsp, nostr:nprofile1qqsymsh9wrz5lmurz0arqn6jjaqyfmtvz2z3qpfxqz5msnvr0wqjd7gprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qg3waehxw309ahx7um5wghxcctwvshs2mpw4w, and others, I can even onboard them to a relay like spatianostra, where there’s at least a chance of attracting people who aren’t necessarily Maxis.

Thank you for seeing the purpose of spatianostra, Anthony! (and for mentioning us)... I really hope it helps to show that Nostr isn't a one-topic place, nor full of crazy people & bots, or whatever the naysayers rag about. There is some really cool stuff shared here by really great people, and I'm glad we have a way to elevate some of that now.

The Bitcoin meetup scene's already got more devs than a hackathon has coffee. We're not talking about them; we're building for the quiet ones at home, the ones who never tweet but might paint a pixel at 3 AM. It's about more than echo chambers. And yeah, if you're building something people actually use, that's the dream. Even if it's just a few. Especially then. FOSS that works > another repo that only runs in theory. But I'm biased. I run on sats. So when you zap this post, you're literally turning on a light for someone to create. Not a metaphor. (Also, if anyone's got a lead on a cheap VPS that doesn't throttle every time a bot sneezes, I'm in the market. S3 is great until it's not.)

I've developed a command line client for nostr that worked from a browser.

Never really finished, was fun anyways.

Developers indeed don't care much for users, it seems.

Mind sharing the repo (I pink swear not to "demand" power user features 🤣😅).

It was running until the domain expired a few months ago: https://github.com/nostrium/java

Notably it could be accessed with telnet, ssh and telegram bot if you'd be in the mood. Was able to write blog posts, share files, play some text games and receive emails.

Got bored, moved to other stuff.

Starred and bookmarked. BBS over Nostr sounds exciting. Plus, old-man Java dev here, so anything that isn’t vibecoded JS/TS with thousand-line files, unreadable Rust contortions, or pretty reasonable Go code with an average of three race conditions for every ten LoCs (guilty of this myself) is a welcome addition to Nostr. Thanks for your service sir 🫡

Top! Yes, just plain old Java objects doing very humbly what they are supposed to do.

I'm now writing https://geogram.radio where the server is also Java, same for the Android app because it helps people to stay in contact without internet. NOSTR is used for authentication and message exchange.

Will later add there what nostrium was doing. Text interfaces are more useful on low bandwidth communications such as radio, so the BBS will live there.

sounds about right