The client should be effective enough to read. Could benifit from better design and to have nested notes, but if the events are formatted well, it should work.
Uploading, let alone doing so from a web interface is a different story 😅
The client should be effective enough to read. Could benifit from better design and to have nested notes, but if the events are formatted well, it should work.
Uploading, let alone doing so from a web interface is a different story 😅
Uploading isn't as important as reading. People won't use it unless they can show someone else what they wrote.
But, yeah, the design is sorta... 😬 😄
Would probably take nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn one afternoon to make it nice, though, and then he can use it to play around with CSS stuff.
🙋 halp plz #smolstr dev here
Do you have any UI benchmarks you like (or just know of) for these kinds of modular articles / books?
Trying to wrap my mind around how to handle all that source referencing, switching versions, opening wikis etc...
Nope. Brand new territory. Nothing like this exists on the planet, as far as I know.
That's why I've been watching these events so closely, but development has stalled and I want to publish, so here goes. 😅

Brand new design territory, you say!? 👀
Opens up an entire sector for magazine and book readers.
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc was talking about a reading apps like Readwise, but you could also make something to rate books like Goodreads, or to write and publish books like Adobe, or an ePaper viewer for Nostr 30023/30040 notes, so that someone could download the note and all of the first and second-level links or embedded items to their cache or local relay/database, to view them offline. Of course, eMagazines and eNewspapers. Etc.
Yep, text-based media is so perfect for these offline use cases since the cost of downloading annex-stuff is relatively low.
Seems like the soft- and hardware (nostr:npub1a00wj229auzjswlq4s77y4u8eqdx5k9ppatgl8rtv8va65f6mwksum9q3h ) are coming together for a pretty great homeschool experience for my kids 🤩 .
I would also just be grateful to have my Nostr reading move to ePaper. The screens are going to make me blind, but I can't print everything out.
I could imagine a homeschool curriculum that uses the original sources integrated into the actual curriculum.
Another thing that would be fun would be an online book club, as that could be both synchronous (daily reading) and asynchronous. Someone who was reading the book could just click on some often-highlighted passage and join the conversation, even if it were a year later. The people in the convo would get tagged and maybe drop by to chat and their own followers would see their reply and maybe wander over and read the passage, too.
I'm planning on doing that, with "The Rhetoric". I'm going to print the entire book as 30040/30041 and then go back, link to bits of it from articles, and add commentary, week by week. And then I'll take all of the articles, at the end, and bind them into a new 30040 collection "Laeserin reads The Rhetoric". And everyone can interact with that or print it out as an ePub and read it later.
Liminal is from the natural sciences, so he was inspired by this https://en.wikipedia.org/wiki/Zettelkasten
They're the basis for wikis, but wikis don't have stable content, so they're actually a different thing. The content of zettel isn't supposed to vary wildly or change 5 times per day. It's something you write down and keep, to use and rearrange later, like snippets cut out of paper.
Yes! Good on point on the difference between snippets of source material vs linking to variable wikis. Noted! ✍️
(Reminds me of the book "Lila" by Robert Pirsig, where the main character Phaedrus uses a similar system of slips to organize his thoughts into a book)
People probably think I'm nitpicking about using different types of events for different purposes, but it's the sort of narrow difference that balloons over time. And nostr's interoperability means that there's no advantage in just using one event-type or client for everything.
We can just make article addresses work inside of wiki pages and wiki addresses work inside of articles. Done.