Video download link | md5sum aa4527c35a4fd949b8fa35a78173e4b1 Images in Tux Machines Over Gemini Creative Commons Attribution-No Derivative Works 4.0



Summary: Any Content Management System (CMS) for the modern Net ought to look beyond the Web; adding Gemini (protocol) support is a nice-to-have, but what to do with images?

THE World Wide Web is decreasing in size and importance. Several data points indicate that this decrease is consistent. It's probably safe to predict that the Web will be a "legacy" protocol within a decade or two; software moves fast.

"At the moment, images in the capsule use anchor text that's inherited from alt in HTML and in turn link to Web versions of these images."We've meanwhile progressed to adopting other Net protocols (Internet, not the Web) and the above video shows handling of images in Gemini (using Kristall and Lagrange; only the former has rudimentary support for HTTP/S, but the latter can handle in-line images over gemini://).

At the moment, images in the capsule use anchor text that's inherited from alt in HTML and in turn link to Web versions of these images. But in theory they could all be served over gemini://. The video shows how that's done in NewsWaffle (Lagrange handles it nicely, but that is a client-level feature; it's left for the client to decide how to handle such images).

"Gemini makes cross-site (or cross-capsule) spying very difficult.""As far as I can tell it is a design feature of the protocol," an associate explained. "The image will always be an external document distinct from the body."

Gemini makes cross-site (or cross-capsule) spying very difficult. Keeping protocols separate and objects separate is an important trait. That also helps restrict bandwidth usage (or waste). ⬆