An incomplete and very rough draft of a NIP I propose that I am dubbing "NIP-151". The intention of this NIP is to have list of of NIPs should implement at a minimum.
Keep in mind this NIP is being created by and from the viewpoint of someone who is not a developer nor completely understands intricacies of each individual NIP. #nostr #nostrdev
https://docs.google.com/document/d/1JXGP3EjDSP0yE7Pxorv27SG7Aj9-834FwJKiuikTiEU/edit?usp=sharing
Good night.
Depending on what client you use, that isn't as much of an issue because they do have a recommended follows list.
Chicken and egg, yes, but some of the other issues amplify that issue.
Yep, less focusing on the "Next Big Thing" and more refinement of what's already there. That and more standardization cross clients.
Weird... I'm trying to look at snort desktop and it'll load the notes my feed but if I click on a specific note, it won't... I'm logged in with alby so that shouldn't be the issue. What the heck is going on? #asknostr
Though is does force me to have a bit of a better understanding of what each NIP is supposed to do.
I did not expect developing a a #nostr NIP from scratch, even one that will contain no code like the one I'm working on, would be so difficult. Then again that could very well by my laziness talking.
A classic #procrastination tactic is to wait until the last minute before saying, "I'll worry about it tomorrow."
That's not bad idea. Just a matter of figuring out what what NIPs should be on that list.
Problem is that I've seen on at least one occasion that when people suggest that there are perhaps too many clients and that people focus on a couple, they got shouted down.
If you're around for long enough you'll notice that most of the recommended follows are vocal bitcoiners and as a result a lot of the conversations surround bitcoin and to an extent nostr itself.
That's a result of the chicken and egg paradox. People aren't joining because most content is centered around bitcoin thus no diversity, and content isn't moving away from bitcoin and becoming more diverse because people aren't joining.
The idea of it having to be every dev for themselves when it comes to developing clients. Why have 50 devs working on 50 different good, but not really great, clients, when they should be grouping up and focusing on 2-3 bigger and more robust clients. To me, this would create a standard of what NIPs Twitter alternatives should be implementing by default. Then again I'm not a developer so keep my ignorance in mind.
That also leads to this feeling of not really knowing what the hell nostr is supposed to be. I use it exclusively as a Twitter/X alternative. That's what people fleeing X most likely want. But we have 50 devs working on 50 good but not great clients that fill 50 wildly different roles. That's going to confuse the hell out of the normies. My peanut gallery take is devs should focus on establishing a large userbase for the microblogging apps, then figure out what roles nostr tackles next.
Yep, nostr devs seem so obsessed with this idea of needing to reinvent not only the wheel, but ever god-damned part needed to to build the car. I've seen the idea of coalescing around a small handful of clients multiple times, only for that idea to be shot down immediately.
For those out there that know #babymetal well enough know how #rare a pic like this actually is. I THINK this is their first official "out of costume" pic in almost 10 years. Maybe this is a sign of #change.

Is posting something for the sake of posting still in line with the #challenge I placed on myself at the beginning of the month? What about a post that states that any conversations I took part of counts? Just some #foodforthought
Bitcoin wasn't even a damn factor in what I fucking wrote. I just meant in general regardless of what tribes may exist here. Good grief!
Not necessarily. Anyone can generate a key pair at any time, but those same people might not understand how all the pieces fit together, and get frustrated when it's not clicking for them. Then they throw their hands up, say fuck it, and leave.
Unfortunately, from what I've heard, onboarding is a bit of disaster still.