On Sat, Nov 14, 2020 at 11:35 AM Alex // nytpu <alex at nytpu.com> wrote: > It's funny > because http actually had client certificates first too (TLS RFC dated > August 2008) and then decided that cookies were definitely needed > (Cookies RFC dated April 2011). > Standardization in the HTTP/HTML world has until very recently been a matter of trying to catch up with what the browser authors are doing. Now the standardizers (the WhatWG) *are* the browser authors. > This is an excellent idea, and you don't even need to extend the spec > for this. > Thank you. It's something I've been thinking about since Gopher days, but Gemini makes it much easier. Another addition is for a client to add a link to a page that you jumped away from by manually entering an URL that points to the page you went to (this would be a forward link). > Caching? Done. Backlinks? Of course! There's another idea that goes with the above; have an "itinerary server" that has access to a specific user's backlinks and cache. That way you can publish your personal view of Geminispace, with the pages as they were when you saw them and your whole path traceable by whoever you give access to the server. John Cowan http://vrici.lojban.org/~cowan cowan at ccil.org Schlingt dreifach einen Kreis vom dies! Schliesst euer Aug vor heiliger Schau, Denn er genoss vom Honig-Tau, Und trank die Milch vom Paradies. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201114/5c19 6ea7/attachment.htm>
---
Previous in thread (7 of 10): 🗣️ Alex // nytpu (alex (a) nytpu.com)
Next in thread (9 of 10): 🗣️ text (a) sdfeu.org (text (a) sdfeu.org)