I apologize for our tardiness in rolling changes out for #Alexandria. We sped development way up, but now the review+merge process is the new DevOps bottleneck. Alexandria is already so massive and complex that the PR process is a trial. We're trying to clear the PR traffic jam with a more continuous and automated process, so that you can actually try out the stuff we're building on next-alexandria, #thoon after it has been prototyped, rather than having to wait until its final iteration. That will also keep us from having gigantic PRs. We're also trying hard to get the #GitRepublicServer moving, so that we can get the #GitRepublicWeb prototype rolled out. Those two products are tightly-integrated, as the app is the viewer for the #ngit server. For now, here is an overview of some of the stuff in review: Pride of place goes to the long-awaited table of contents, that nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn is building. This is much harder, than it looks, as its a lazy-loaded ToC, to match the lazy-loaded publications (the solution for gigantic publications running smoothly), and aligning all of the various reactive bits is tricky. https://i.nostr.build/z2vsC2UTZskU0PPF.png https://i.nostr.build/j64NsSX6f5y0gI44.png https://i.nostr.build/KtlMQNDybzCRlC41.png It actually almost-works, but he has to go back and rework it for blog posts, viewing individual articles (30023 and 30041) and wiki pages. https://i.nostr.build/iIghKXPcLGAXIKLp.png https://i.nostr.build/Q3KMAo920ZAn8M3K.png We've added npub (read-only) and amber (read and write) logins. Since we have a reader, the read-only login is actually useful for most of what you do with the app. https://i.nostr.build/YOAwFmInDYDzVLA6.png https://i.nostr.build/8FIQbfoZyEoJqE3D.png The landing page is now completely reactive. It loads all available publications, and displays them in pages and according to the width of your screen, with the search bar "finding" publications that you can't yet see. https://i.nostr.build/CtCWQQhVUmbiWAk3.png https://i.nostr.build/5IVQOzm3Eg0rydF2.png The about page has a relay connection status view, which I use for testing. https://i.nostr.build/BJXiMKvugaB2F2GE.png We implemented syntax highlighting, MathJax (LaTeX), and PlantUML displays, for Asciidoc and NostrMarkup parsers. Prepared it for BPMN and TikZ rendering. 30041: https://i.nostr.build/bZmJZlkiHXWTulE5.png https://i.nostr.build/aEuyrqBbEd3nVLMt.png 30023: https://i.nostr.build/5quFU2cKvvDXj3Cs.png 30818 (those are wikilinks, at the top, but remember that you can put wikilinks in any event, now, and Alexandria will display the link, properly, and navigate to the rendered page when clicked): https://i.nostr.build/2d2cT1zCb8dhZhnO.png And the feature I'm already addicted to is the Events page, which allows you to search for any event, displays the event in its original state, and lets you reply to any event and publish any event (yes, including 30040 publications!) The d: search is for d-tags and second-order events (things that quote or respond to the d-tagged events found). https://i.nostr.build/CzFvHLpyD5PuRRoT.png https://i.nostr.build/oAXhrwvdKnIJs8KN.png https://i.nostr.build/tWLD618ComQWvuXW.png https://i.nostr.build/tWVLHZ6E0wHCfrVr.png https://i.nostr.build/g3JwKixIk4GVvu52.png https://i.nostr.build/C0agFp7yyjKS64m8.png https://i.nostr.build/ZomqsN3OaVtdUA8o.png This is *not* the Awesome Search Page we're building, but just something rudimentary, to hold everyone over until GRW comes out in protoype. We need to build an entirely new architecture, based on an entirely-new tech stack, to get that working. We've officially hit the #ScriptkiddieWall, where the architects and engineers need to roll up their sleeves, to get things built. Good thing we have some architects and engineers. 😊 But, first, they must work through the Merge Conflict From Hell.

2
3
3

1
0
3

1
0
3

GM Nostr, We've been working on a number of projects, in the background, including a Nostr-based git HTTP server, and we've been considering our pricing model for them. We have received enough donations to reserve the git server, and nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 and nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 are going to be launching the beta version of that #thoon. We are excited to use it, ourselves, as it's frustrating fighting other login methods. Nostr is simply less friction. We are aiming for a base storage of 1 GB for an organization (the owner npub and the collaborator npubs it invites), with additional storage purchasable. 1 GB is more than most dev teams use, and we want to keep our running costs low. If it turns out to be too little, we will increase the baseline. It will be bundled together with a media and blossom server, and a subscription to theforest (we will credit you anything you have paid for theforest), as well as access to our other inhouse systems. This is also just a fun way and easy way to help support our efforts, and to make sure your support requests get faster responses. The subscribers will be invited to help us Design Think our systems and applications. *We build with you and for you!* We are also negotiating group discounts from other service providers, which will be offered to anyone on our NIP-05 list. We will be controlling access to those servers, and to the other functionality we have planned, over the https://gitcitadel.nostr1.com relay and the gitcitadel.com NIP-05 list. That is a read-protected relay, unlike https://theforest.nostr1.com, and any Gitcitadel team members you see on there have paid for the access, themselves. nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl is the first user. 🙂

2
0
3

1
0
3

2
0
3

0
0
3

Nostr itself is a wiki (hat tip to nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q for that idea), but it also has specialized wiki events. You can view them over the URL bar, already, and some of the publication content is actually 30818 wiki pages, not 30041 sections. Example https://next-alexandria.gitcitadel.eu/publication?d=mirepoix is the same as https://wikistr.com/mirepoix*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319 And this document only contains wiki pages, arranged in a 30040 index: https://next-alexandria.gitcitadel.eu/publication?d=gitcitadel-project-documentation-by-stella-v-1 However, what happens if "mirepoix" has two results (it does)? Currently, we show the newest one, but we will #thoon be showing a wiki disambiguation page. It will display the wiki pages prominently, at the top, and allow you to CRUD your own, defer to or recommend those from others, etc. But it will also have a semantic/topic search bar that will return wider results from the community (which, in our instance, is theforest 🌲), regardless of kind. So, when you type in "mirepoix", this here kind 01 note will appear in the results. You will also receive pictures people have posted about soup vegetables, videos of soup veggies being chopped, recipes people posted in 30023 notes about making Suppengemüse, etc. And you can then filter and sort those results, like on the publication feed. So, if you want to see everything anyone on Nostr wrote about "Wuthering Heights", you go to the wiki page and type in "Wuthering Heights" and we show you everything we can find, with any wiki pages (which are essentially curated search results) on the top. We will find more or less, depending upon which relays you have access to. Every page (publication, wiki, articles, events, visualize, social) will be both a navigator and a viewer, and context-sensitive to the page. Because we're a library for Nostr and the Nostr library contains all sorts of library items. Modern card catalogs are semantic search engines.

0
0
3

0
0
3

0
0
3

1
0
3

1
1
3

1
0
3

1
0
3

1
0
3

1
1
3

0
0
3

0
0
3

0
0
3

Hello. We have a new feature implemented, in #Alexandria, which might interest some of you. We have revamped and expanded the index card menu. You now have the ability to display publication details (index metadata) on the cards, including book summaries, ISBNs, and links to the npub profile pages of the publishing npub and the author. (If the author has a npub and is referenced in the 'p' tag, as with nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc's book, below.) https://image.nostr.build/0fba9c50c6f155a5fcad0f9259ff27339b260ef8b6f583a9f9498f30970c02ea.png This allows for publisher and author to share in the credit and the zaps, and to both be notified of interactions with the index. https://image.nostr.build/88ba49e743f87fb893f430a07d089e1aa8109b3137dcbd562ef3dc0c17acb207.png https://image.nostr.build/6d92fb472b3678a641f251d79628fa762b94366a8f61b8e16918c74aaf716549.png You also have the ability to open an original URL-source of the publication (usually to a web page, PDF, LaTeX file etc.), even if the publication is also available in event form. Currently, it opens outside the app. https://image.nostr.build/81bb15d3468f11e57627b12571756e2528e48d2b50c42bf1bb1b9e2823546365.png https://image.nostr.build/b6864db5b020bb31b99f2ae4d01b746e0942701a269ef19b370ba3e2a48f05fe.png This opens up Alexandria to being a true library catalog of all publications, even those under copyright or where there is no digital version readily available. They can be referenced and interacted with, through the index cards, in a manner similar to GoodReads or other "book review" sites. This will become more apparent, once we add things like kind 1111 comments, to the index events. For now, we're still revamping the parser and the table of contents, but they should be replaced #thoon. Thank you for your patience and support, while we rebuild, and may you have a good evening. Happy reading! https://next-alexandria.gitcitadel.eu/

1
0
3

Showing page 1 of 3 pages