What y'all are doing is hella impressive. Pumping out quality work with a shoestring budget, exquisite minds, and hearts of gold.
nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf has built some cool stuff, for the Visualisation page, and I'll reveal that, when it gets further up the merge traffic jam.
Discussion
We need to get it merged, tho. 😭
We can barely build new things because they depend upon other new things that depend upon other new things, that only exist to allow for other new things...
Concrete example is the ToC. When he started building it, we had a viewer that just loaded and displayed 30040s with 30041s listed using "e" tags.
Easy-peasy.
Then we switched to "a" tags and broke the ToC.
Okay, hide ToC and update ToC.
Then we switched to lazy-loading.
Okay, update ToC.
Then we added support for viewing individual articles.
Okay, update ToC.
Then we added support for blogs.
Okay, update ToC.
Then we added support for wikis.
Okay, update ToC.
Then we added support for longform.
Okay, update ToC...
ToC never gets merged. 😂🤦🏻♀️
So, there's now this powerful everything-viewer, but there's no ToC. Everyone like WHERE TOC??
this reads like the story of me trying to contribute to LND
Yeah, and it's a never-ending story because our publication viewer is going to support any event with a content field, regardless of kind, and integrate the display of citations, and render everything everywhere, so things are gonna get even crazier.
And the ToC just has to
And that's why nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn is the one stuck in the development basement, while we all stand around and stare at him, battling the ToC on his own. Nobody else can build it and he's the boss, so the bugs stop with him.
Gitserver is the same deal, except that it's nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 in the ditch. 😂
Me: So... you done building Thing I Don't Really Understand?
nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 : Ummm... No, not yet, sorry. I've got to Incomprehensible Tech Blah Blah and then I need to integrate this portion of the Complex Scribbles on a White Background With Arrows and Boxes diagram and then nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 will move on the Etc Etc Something Something script thingy.
Me: Oh, okay. Umm, okay. Sounds great. Well, I built an app that integrates all of that and I've got 18 PRs all set up for your review. So, look at them, when you get a chance. But finish the other stuff first, real quick. Whatever it is.
Apologies for the delay.
I truly am sorry for being unable to find enough for time to push it through 😢
also, there probably is a problem in that you need to have the titles of sections in the index event? as the third or usually "relay" field of the tag? otherwise you'd end up having to load and parse all the sections which i guess you already sorted this out but just made me think of it because a ToC on a segmented document has to have some reasonable text to load without touching the segments
The section headers get removed from the content and placed in the section events' "title" tag, with discrete headers untouched.
We lazy-load the sections, as you scroll down and as you open up levels in the ToC. We therefore have to handle someone opening up a level in the ToC, that hasn't been loaded into the reading panel, already, like a fast-forward viewer, but just of that section. The sections inbetween get filled in, as they scroll toward the already-renderd sections.
Or something like that. I think. 😂🤷🏻♀️
When you try it out, it is really underwhelming. Click ToC text, jump to section in publication.
That the publication can have 30k sections and you've only loaded the first 200, but you can still jump to sections 8018-8020, and render them on the fly, is completely invisible to the user.
But that's the Biblical use case and we promised that would work, so we're making it work.