can you tell me more a bit about the doc kinds and label kinds? have some ideas. nostr:npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy is a force of nature.
The issue is that users are sharing guides of nostr through kind1 and articles, but anything in kind1 just gets lost after a few hours - using ndoc we now have a way to surface them back up - maybe eventually incorporate them into our nostr knowledge base Alexandria as some collection of guides.
And yes, force of nature regardless of her denial 🫡😁
Here's an example - just a comment with the hashtag referencing a nostr guide
cool, but a dedicated kind would work better in grimoire since it's just a CLI DSL for single REQ queries atm. there's this kind for labeling (1985) from NIP-22 that we could use, fetching all the labels that say ndoc and embedding the original content + label when rendering event. the comment kind or note kinds are too generic to show full "replied to" if that makes sense.
Hmm yeah, am aware of the labeling events, but creating them is less convenient for the general user.
Just allow me to think out loud, not any sort of calling out.
This kind of tagging process is possible on any client, which users will try to find a way to do it - they're not looking for specs, they're not looking for labeling tools - they'll use any means available with the client they have, which IMO is something to encourage and adapt to.
For what it's worth, I would be willing to label ndoc stuff with some labeling tool, but neither of the ones that I know of, work. Spammy looking hashtag comments aren't ideal but they do create a nice cohesiveness... until the hashtag gets highjacked, of course. If there is a better way to approach this to help make that content more accessible, I'm all ears.
Emergent organization will happen anyway. Nested quote notes to keep track of daily music posts broke Amethyst - but it fundamentally was done because of a desire to organize. Kind 1 is the most viewable and interacted type of data on nostr, and its inevitable. nostr:nprofile1qqsyawyrzrttfmv4cmtx5w2m85702kdct7hv3amfrkhagpdf9cz46mgpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uq3kamnwvaz7tmjv4kxz7fwdehhxarjwpkx2cnn9e3k7mf0aur9gg has a number of hashtags to organize her content, recalling them.
The whole 30040/41 event spec was built off this fundamental desire to organize events into larger structures, which generalized, applies to a multitude of knowledge organization systems. If there aren't intuitive up front ways to organize our ideas, they will occur one way or another.
I often make little guides & tips for Amethyst. I wish there was a way/place to have them centralized and linkable for people to see, modify, and expand on, other than kind 1 notes I post them as. Am I missing something here?
#makeuserdocsgreatagain
Also appreciate your guides, be it the mobile ffmpeg, nested amethyst secret emojis - all fundamentaly valuable - what I've observed is that connecting and navigating them is a frustrating task across all short note feeds, which is why Alexandria was built - to connect the various notes and specifically be interoperable across clients, aggregating both general nostr and client specifc hints and tips.
Imagine viewing blog and wiki posts just as you would on Amethyst, but you can walk around connected and related guides because they've been all grouped together.
We also just added commenting and highlighting to our articlesv which is also interoperable with Amethyst.
Our first use case. Client specific FAQs
The point was for each client to have a tab that opens up to their own relevant wiki, curated by app developers, or completely open and permissionless - where users are able to contribute to a nostr-wide knowledge base, everything from how to set up relays, what is outbox, how to connect a wallet, to creating nested secret emojis.
First guide "Amethyst FAQ", written by nostr:nprofile1qqsvyv8d6dx2tjp33069j2kq2mx7xage6w2upyzvxl4pcegt3t22wyspz9mhxue69uhkummnw3ezuamfdejj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uq3samnwvaz7tmnwpshg6tp94shycmpdesjucm0d5hsyvtxr6
Am I making any sense nostr:nprofile1qqsda2memtapc2lykjnd8t9px4ake2stw39lg6k49xj6u3jz3pteu6qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9ekxzmny9uq3zamnwvaz7tmwdaehgu3wwa5kuef00ul2u0? You literally just asked "I wish there was a way/place to have them centralized and linkable for people to see, modify, and expand on, other than kind 1 notes I post"
This #ndoc mission is generalized and encompassing if any information that could be deemed as educational & nostr related, whether its introductory info or dev-level. Anything from basic protocol flow stuff to client specific information.
I'd be thrilled if you would include the #ndoc hashtag on those tips & guides along with Amethyst's hashtags. There's far too much stuff like that out there for me to catch it all.
