🎯💯
Also, my request is also that people rethink pouring all of their knowledge and wisdom into Kind 01 notes and consider writing long-form articles and pages, instead.
Wish #Amethyst would let me fork/edit longform+wiki notes. The walled garden is so strong! 😭
You're the only one who has read what I wrote, apparently.
Kiwi browser + nos2x is a foss android solution for web apps that require browser extension login
Kiwi browser is based on chrome and has not had an update in YEARS, therefore riddled with unfixed vulnerabilities.
Yike. Thanks for letting me know. The walled garden really is too strong lol
Long-form articles are going to be one of the most popular entrances to Nostr, as they will start getting picked up by search engines, as they usually are high-signal.
Does nostrudel work for this purpose?
I don't think so. I just tried Yakihonne, but it crashed my browser by creating authentication messages in a loop. 😂 Probably use Habla or Highlighter. Freerse is nice, but it has a mistake in the tagging that needs to be corrected.
They are also the documents that we will tend to archive (long-term, for free to the writer) and promoting in Nostr-internal information searches. That is, after all, why we are coming up with specific relays for this data, such as wss://TheCitadel.nostr1.com
I've said many times that tweets (= kind 1's) should be short. Long-form tweets are an abomination. nostr:nevent1qqs9wne3mc232wez06ndxaaprkgf6p23cwfx3ecyh4rktletzx786mgpr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9upzqmjxss3dld622uu8q25gywum9qtg4w4cv4064jmg20xsac2aam5nqvzqqqqqqyzzt49v
I think she is trying to get everyone to write for other Nostr apps like wikifreedia. I read it as hey take those short notes and expand to add more to the long form Nostr apps, nothing about changing the current kind 1s .... I don't know what kind 1s are but I'm assuming it's short tweet like notes ... She wants people to build their words. But I could be wrong ... She has been asking people to write articles for weeks now. We ALSO need dorks who like to write long form. I think it's two completely different points of views that is needed.
You're correct, these replies we're posting to each other are examples of kind 1
No, you're 💯 right.
This was meant for Sarah SoupBox [Zap.Cooking]. The clients are so willy-nilly in reply-tagging. Hard to tell who is responding to whom, sometimes.
I knew you were talking to me 💐
I get this, but there needs to be an intermediate “kind” then. Some posts take more than 140 characters, but don’t merit full long-form, article treatment.
The difference between articles and tweets is not primarily one of length.
Whatever it is, there are many cases of wanting to say something that requires more space than a tweet, but that you don’t want to be archived as one of your longer-form pieces, lest you dilute their quality. But I agree there is something elegant about succinct Kind 1 posts of the type Gigi has in his thread.
The problem I've had with 🧵on Nostr (as opposed to X) is that they tend to arrive disjointedly, incompletely, or in the wrong order (or the client reorders them). So, I try to space a complete thought over multliple posts and someone jumps on one section and ignores the other parts or can't even see the others. They can't do that, with an article, as if they link to it at all, they always link to the entire thing.
I’ve found on Twitter, the first post gets 10x the views of the middle posts when you make them into a thread. I’ve found on nostr, few people engage with the long form post kind (you allude to this in your article), and more engage with it in Kind 1. But I’ve struggled with this general problem in my work for a while. I have a substack. I only send out long-form, more thought-out, edited posts to my email subs. I want to post more, and I have a ton of ideas, but I don’t want to fill up their email boxes with posts like the one I’m writing now. Where to put the intermediate ones if not Kind 1 on nostr/Twitter?
Since this is a software project, we can actually agitate for them giving more pride-of-place to articles, but only if we use the kinds. They respond to the user's habits because they don't want to waste their time. That is why I'm going to engage more with articles. If you go there, they will build it.
And it is really helpful to the devs if their users write technical documentation. That is often of higher-quality, more avidly maintained, and more targeted to users who don't have insight into the code. It is also an indirect form of beta testing.