Another thing Nostr brings is WORA (write once, read anywhere). You publish your paper to Nostr and it immediately shows up in every client that handles that event type.

That's completely different to a static document file, where you have to apply to this or that committee or website, and then send them the document or whatnot.

Everything automatically ripples out to the relays and clients, on Nostr. And, if you update the document, that update also ripples out. We have a relay that will do versioning of changes, too, which is cool.

Reply to this note

Please Login to reply.

Discussion

You folks are working on a ton of great stuff. This is the future I want to see.

But it's a Nerd Future, not an Influencer Future, so it's hard to get any publicity, on here, but oh well.

It will get built and be used, even if only people who can #NameTenBooks can be bothered to look at it.

There are actually a lot of nerds, out there. Nerds are a huge market. 🀣

people who never lost the love of learning and building

πŸ«‚πŸ’―

Agreed. Basically any academic I interact with has at one time or another complained about the issues with the current paradigm for disseminating scientific work. I'm not talking about politically charged research, just genuine scientists in apolitical fields trying to push the boundaries of knowledge.

Content through nostr is the kind of thing they subconsciously know they need but they just haven't seen the potential for nostr yet.

If we build it, they will come.

I really hope so. I'll be doing my part.

A big drag on this evolution will likely come from the parasitic science publishing industry, but probably also from funding agencies, and even the researchers themselves to an extent. The publishing monopoloy gets fat margins for doing essentially nothing aside from hosting. They do none of the research/validation/peer review/advocating. Funding agencies will complain that they don't have any other way to decide which research to fund because they rely so heavily on manufactured metrics by the publishing industry. Academics might be reluctant to change when their careers are on the line.

Surely you've thought about these issues before, so I'm curious to hear what you think.

Yeah, that's why this only works on Nostr. Every person can publish to the relays and they're done. They don't need to host anything or etc. since they're using the same infrastucture used to post cute cat pics and Bitcoin memes.

And you can publish from an anon npub over Tor, you know. Nobody can tell who did that.

Also, Nostr brings the potential to create other, more modern quality measures, through curation, annotation, remixing, AI, and WoT.

Also, Nostr adds the public discussion. This is really important.

Would you rather have some paper, buried 20 pages in, to a journal hardly anyone reads, or have your paper trending on social media and getting you invites to podcasts and etc.? There's a reason, why so many scientists are on social media. Be seen, engage, get mentioned, or your work is irrelevant to the wider discussion.

Trending/not trending is not really relevant for me since the impact of research can take years/decades to pop off. Yoshua Bengio is a great example of this. Nobody cared about all the fundamental ML algorithms he was coming up with in the 1990s/2000s until deep learning took off in early 2010s and those old publications were suddenly getting cited thousands of times a year.

The transparency and openess that comes with searchability and possibility for public discussion are much more interesting to me. They go hand-in-hand.

Well, academia was practically a village, back then.

I didnt know about Alexandria either. Sounds brilliant. Where can I find the code for Alexandria clients / relays and converters (assuming its all OSS)? And is there a guide on how to convert a document starting from, say, Markdown or AsciiDoc?

I convert with my own parser (which is too ugly to share πŸ˜…), but there's standard converters like Pandoc.

https://pandoc.org/

Thanks for the info! Now I have a good excuse to explore GitCitadel as well.

Just to make sure I understand the second sentence, by "there's Pandoc", you mean using it to generate the AsciiDoc contents for each individual kind 30041 content "section" correct? (If I got this right from this link.)

What I was trying to ask is whether there's a tool that, given an entire Markdown or AsciiDoc document (possibly with some metadata comments), it generates both the publication index and content events for me. Or is Alexandria's UI the best way to handle this for now? (Hopefully, my question makes more sense now,sorry if it was unclear!)

Also, one more question if you don’t mind. Is there a group where people are discussi Alexandria, especially its more technical aspects?

Well, we have a Slack for the project team but nothing on Nostr, yet. It hasn't really interested anyone else, so far.

Got it. I'm not sure if you wish to open it to other curious devs. If you do feel free to DM me an invite to the Slack Workspace. I'm interested for sure :).

It's an implementation-focused Slack, not generalized for all 30040 clients.

Best thing is to DM nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn . He's the product owner, so that's up to him. He's always interested in more devs, if you want to work on the Alex project, specifically. 😊

Pandoc is a converter that can transpose a file from Markdown to Asciidoc.

This is my CLI for uploading test data, but the Alexandria "New Note" menu item should be opening, soon. Took it down because we're revamping the parser.

https://github.com/SilberWitch/eBookUtility

Almost any relay can handle the events. Our web client is community-based, and it displays the community relay only, unless you login (then you can see everything from your inboxes).

Oh IDK, I think this could hit a much broader audience... To me this fits in pretty well with projects like Bookdown, which is a way of creating open-source documents for publication using R notebooks. This is a way towards "reproducible research" in the sense that data analysis methods and calculations can be embedded directly (hidden) into the final document that gets published.

The "atomization" part of this is very similar to what's used in constructing both R and (the more popular) Jupyter notebook, where each "code chunk" can be separated in a similar way that separate verses / paragraphs are, as you previously mentioned.

But yeah as I write this... still Nerd stuff πŸ™ƒ

πŸ˜…πŸ’― Totally nerdy stuff.

It'll be cool, once we get publishing from Obsidian down. That can handle Asciidoc, not just Markdown. Few know this.

Feel like Obsidian geeks are a market for us.