This seems like the easiest route for the masses. Not everyone is comfortable with downloading and converting files into a separate app that they had to previously download. If you can pull it off, I'm 100% behind you 🔥🔥🔥
We basically need an njump-style client, like nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 built, specialized in browsing long-form (wikis, articles, and modular/books). Stuff that stays relatively static and takes a while to read.
And it should allow for highlights.
Discussion
We can, but not until next year.
We have GitRepublic to release first, and that's basically going to be a Nostr IDE. It's a monster. 😂
Oh I must've missed that note? What's GitRepublic? Please and thank you.
It's basically a Ngit-based integrated development environment for programmers. Like GitHub, but locally installed on WSL or Linux.
Very low barrier to entry, as they could read all day without logging in. Just need to login to annotate or to limit to WoT.
That makes it more like a library, where you can just stroll around and look.
Love this thought process. 🔥🔥
What do you mean by "converting files into a separate app"? What weird context am I missing here?
The average Kindle user just uses books on their kind. They don't download epub files and import them to a third party app or convert them from one file format to another to consume them.
OK, but what does have to do with anything? Is nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl proposing a way to publish books on Nostr that is compatible with Kindle?
Not compatible, comparable or an alternative to Kindle. If it's done as a low barrier to entry e-reader website, then people could use it as an alternative to their Kindle. They would not have to download epub files and import them into a separate e-reader application. They just visit the site and that's it. Easy reading.
Yes, an e-reader friendly Nostr site for books and anything else in long-form.
All e-readers have a browser.
Also ideal for tablets or for people (like me) with bad Internet connections or crappy hardware.
If you look on Project Gutenberg, they have all of the different filetypes already created and stored, probably with a database.
Nostr already has a database, tho (relays, an event store), where we're storing the books as events, which are the smallest, simplest building blocks of such documents. So we can always work parts-to-whole and generate any other view on the fly, including HTML. With a book, you don't need the speed and convenience of a websocket, as the text hardly changes and there's hardly any interaction. It's just you, staring at a long text, occasionally highlighting something interesting, and maybe submitting a review of the book, at the end (like we do for relays).