💾 Archived View for bbs.geminispace.org › u › oldernow › 12071 captured on 2023-12-28 at 16:43:53. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
And, of course, now I'm realizing not all links are going to be gemini:// links, and of course getgem fails on them, making all https:// links look bad... :-) It never takes long to re-remember why I eventually couldn't do software development anymore.... :-) So I guess I'll play with using cURL against https:// links to at least cover that case, which I imagine to be the most frequent non-gemini:// case....
Nov 30 · 4 weeks ago
It is probably best to run this as a separate tool/script as you've noted. It is effectively a little crawler, after all.
An interesting related feature in Lagrange could be the creation of an offline archive by saving contents of a capsule and all of its linked pages up to a chosen depth. That would also determine if any links are bad.
When it comes to making too many requests, multiple ones spaced out a few seconds apart are already too much for the lowest-end hardware running servers in Geminispace.
🍵 michaelnordmeyer · Dec 01 at 07:37:
What happened to Gemini's paradigm "one page, one request?"
☯️ oldernow · Dec 01 at 16:29:
Now that I know the "two finger tap" trick to properly display a working context menu in Lagrange, exercising my "check links" code goes like this:
@skyjake that makes me wonder whether there's already (or might be in the future..) the means to customize the "context menu"? It would be nice to be able to add an action that calls a user script to process and return a modified version of the page being viewed - in place. Then the above list could be reduced to just the first bullet.
At the moment, there is no way for one to add actions to the context menu. It's a nice idea, though. I'll add it to my list of things to do.
Lagrange plugins? — Lagrange plugins? (Apologies in advance for being took lazy to scan Lagrange documentation, and for likely using clunky terminology in what follows.) Does Lagrange support adding something akin to a plugin that Lagrange would pass the gemtext about to be displayed, but then *instead* render the gemtext modified/output/passed back by the plugin? I ask, because I played a bit with a simple "detect bad links" idea, which at the moment is this Lua script: [preformatted] In...