The idea that every tweet needs to be a wiki is a solution in search of a problem.
Discussion
💜🤣
Let the chips fall where they may, and we'll have innovation along the way.
Yeah, but fair game to point out that someone's new feature might be a bug.
Not every NIP is a winner.
Not every change is an improvement.
Sometimes developers just build stupid stuff because someone gave them a hammer and now everything looks like a nail.
1) Also, I think we're losing sight of how much the lack of complexity contributed to the success of Nostr, so far. That was feeding the innovation and kept the applications light-weight.
2) We're trying to build a SDK for a very simple, basic client, and it's a big ball of NIPs.
And now everyone is under pressure to implement edits and these stupid tweet forks, so they're going to want that in the SDK, so it will take us twice as long to finish.
Can you point me to your git repo?
I agree with you. There are so many NIPs.
We aren't publishing everything, until we're done, but here's a little sample he published in his personal repo, as proof of building.
https://primal.net/e/note1zf3udv3f7xl2tphsa2573hazcpesd5m56w7fs3z3vxgp3ver30lshg9j6a
Thank you for sharing.
We realized this was stifling innovation, by leaving smaller development teams with way too much front-loaded work, just to get a Kind 01 feed going and keep up with NIP changes, so they are often using SDKs and we think they need more SDK choices.
But now we're the NIP bagholders. Especially anything that messes with the Kind01 feed dramatically is like ugh.
What are some SDKs that help you build a client?
This is probably the biggest one
https://github.com/nostr-sdk/nostr-sdk-ios
This is just a client library, but probably also interesting.
I will look into these. Thankx
3) Throws new development back weeks or months, unless you do this full-time.
So, it feels like an attempt to shake off new competition, that was going to bring real innovation, through a form of protocol capture.
4) You know what I'd like to see? Threads. 🧵 That's something real writers often really like.
But the guy who wants to build it for me is now busy trying to figure out tweet forks. 🤦🏻♀️
Threads somehow are a huge blindspot for devs.
It was the n°1 reason why I liked Twitter.
I don't know 1 client that displays them properly, let alone incentives their creation on the "New Post" screen.
They gave us tweet-forks instead.
And now, they're like, "Please, clap."
Me personally I'm a threads hater... It's basically just a blog post split into > 20 different chunks. The reading experience on Twitter was terrible unless you used TwitLonger to turn it back into a continuous text again.
Nostr has long form content which obviates the need to do this in the first place. Having the thread as a single article in markdown with headlines and such is about 1000x more pleasant to read IMHO.
You can just have an option to read it, either way. 🤷♀️
The goal of threads is to allow people to interact with specific parts of a longer entry, and to encourage writers to think in concise ideas.
💯
Take away those limits and you remove the high signal great threads typically have.
Displaying them as a actual threads also offers the most efficient ways of interacting and sharing.
However you choose read them, if that's your main goal, is up to you (especially on an open protocol).
I agree, but I’ve learned to accept that even what we had previously established is ok to question and retry.
Welcome to the random walk 🤓