I'm going to try and #asknostr for this.
The client I'm working on is more or less about making full articles out of smaller notes, the purpose for this is to isolate individual ideas and concepts of some larger article. A bridge between very long articles books or wiki pages and small-specialized personal knowledge bases (zettlekasten).
Why? Think about a wiki, but with multiple perspectives per topic, and the content of each article can be some sort of mix of any other article's content.
If you want to write about some sort of level 3 concept and other's have already written about levels 1 and 2 perfectly well, why reinvent the wheel? Academic papers, textbooks, blogs and tutorials are filled with redundant content like this and always hiding background content in references. What if those references were a part of the article itself? I think that this could lead to a new way of consuming knowledge content, and would like to build it with the community.
Looking for advice on constructing this to keep interoperability with other clients while also not spamming feeds with tons of Kind:1 notes. I'm trying to spec out these kinds, and some possible metadata tags. The kind(s) might lie somewhere within the 30000-39999 range of parameterized replaceable events.
Two basic types of kinds
- Article metadata and list of connected notes
- Notes with isolated concepts
This is related to the Kind:0 (user metadata) and Kind:1 (text notes), but for an article that can change its structure and content as time progresses and knowledge about a topic updates. For the time being, I'll just refer to them as ArticleKind:0 and ArticleKind:1.
- ArticleKind:0 sketches out the structure of an article at a point in time. It has the article metadata and the specific list of notes that compose that article. This specific kind is what would be displayed as a preview to users. One possibility could be embedding the structure of the article in this event.
- ArticleKind:1 contains the content, subsection title (introduction, tutorial B, ingredients etc.) and possible references to external content. The subsection titles can be aggregated to create a composed table of contents. Similar to ArticleKind:0, a possibility could be to embed the immediate connections of this note (e.g. previous and next notes, which can be single or many notes)
Why replaceable? If information is updated the most recent article/note will display, but a living history of the document remains (if relay operators decide to not delete old notes). Articles/subsections can exist with multiple perspectives but can be linked together by single ArticleKind:0.
Isolated concepts help both writers and readers focus on the information they care about while allowing users in the future to compose new articles out of previous notes.
What you can potentially make is nonlinear-modular-chooseYourOwnAdventure articles that let you read and write about topics in what whatever fashion you'd like, while allowing already well explained work to be part of your article.
- You want a regular linear book, that's fine.
- You want a branching story? Go ahead.
- What about a weird ouroboros spaghetti linked article? Why the hell not?
Further reading:
(brief, possible applications)
- https://github.com/limina1/indextr-principles/blob/main/README.org
(longer, drawn out concepts and rational)
- https://github.com/limina1/indextr-principles/blob/main/details.md