GM Nostr 😊
Things are finally moving along, toward the full release of the Gutenberg edition of #Alexandria.
We have a stable v0.0.1 on https://alexandria.gitcitadel.eu and the (buggy, very much alpha, but feature-complete) v0.0.2 has been rolled out to our staging area on https://next-alexandria.gitcitadel.eu.
This iteration adds the features:
* Table of contents (a work in progress, but fun to play with)
* Events search page for
* unique IDs (hex, npub, naddr, nevent, note, nprofile, and NIP-05)
* n: name
* d: d-tag
* t: hashtag
* Publishing of any event kind, including 30040 publications
* Commenting with kinds 01/1111, for any event
* D-tag/wiki disambiguation, that respects deferrals
* Relay and network monitoring
* Automatic detection and integration of local relays
* Rendering of long-form articles, publications and notes, wiki pages
* All content fields rendered with #NostrMarkup, either Asciidoc or Markdown, depending upon the kind
* Login with browser extension, npub-only, and Amber (remote!)
* Note (30041) composition
There's a link to a short mobile screencast, on our Geyser page:
https://geyser.fund/project/gitcitadel/posts/view/4803
You can see, here, how the event viewer panel opens to the right of the search results list. Unfortunately, this looks really messy on mobile, so I didn't include it in the screencast. Will be corrected. I'll move the panel below the results, rather than to the right, to accommodate the narrower screen.
The golden stars denote membership in the instance's community (in this case, subscription to https://theforest.nostr1.com. We will have silver stars for other verifications, such as the one nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is building for nostr.land, and the meetup attestations from nostr:npub1purpleye8gzrzss99nzqqnemtf7g8xxj8p950nkyknnuqzycuh5qnazkzp . This is a higher-level of verification, on top of the normal NIP-05s.
If you wish to create curated publications, please use the form on the Events page, not the Compose menu item. Simply enter the information, like so, with the content field simply being the AsciiDoc file, copy-pasted in.
The form cannot yet handle AsciiDoc metadata, but that will be added to the parser before release. For now, simply manually enter the tags. The title and d-tag are generated from the document header. Try to give your documents unique names, so that you can recognize them, later, by title.
I don't know how large of a file it can handle. It will need to be tested. But go ahead and give it a spin.
Showing page 1 of
1 pages
