The best thing for nostr:nprofile1qqs06hur0durup4gswajdrter25f5zhd7vpf9xnu34k8znh877mzngspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp07y68w8 experts can do right now is just write about their ideas on nostr, especially like long form blog/article. Nostr has pluralism (https://en.m.wikipedia.org/wiki/Pluralism) baked into its very core, so MedSchlr aims to embrace and amplify that as a medical+health+science+research+education focused knowledge commons. Sharing your ideas, providing thoughtful criticisms is the best way to facilitate the growth and efficacy of MedSchlr. #Alexandria, as a base nostr client brings it all in for further conversation and idea evolution.

#Alexandria is focused reading and writing, rather than a social focused app. Think about something that brings together personal notes, annotations & highlights on all types of writing. From literature, to documentation and scientific peer reviewed articles. The community sets the standard for what is allowed. So an example: (1) you have your fiction community that holds a library of books. (2) The academic community that writes articles _about_ Ulysses and (3) The person reading Ulysses on their own free time, writing notes, highlighting and referencing the academic articles, connecting the ideas together. And then, because the work has been done on nostr, anyone can follow the trail and learn from what other's have done,

Make Apps Beautiful Again #Alexandria

I'll eventually have a python version, for #Alexandria, but I'm in charge of PHP implementations, so I'm doing a couple of small projects with that, to warm up. I was just doing databases for a couple of years. I like the PHP Helper library, tho. Recommend.

I'd like some design feedback on Alexandria. I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events. My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes. Question: How would you like to preview your published events? I see two options: 1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events. 2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events. I'd love to hear people's thoughts! #asknostr #alexandria #gitcitadel #nostrdev #nostrdesign