Thread

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 @npub1wqfz...qsyn 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. 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. 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. 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. The about page has a relay connection status view, which I use for testing. We implemented syntax highlighting, MathJax (LaTeX), and PlantUML displays, for Asciidoc and NostrMarkup parsers. Prepared it for BPMN and TikZ rendering. 30041: 30023: 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): 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). 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.