>> Gemini spec does not mention caching, and the FAQ says: >> >>> Gemini has no support for caching > > Perhaps this should be rewritten as "no support for cache control". This would clear up any ambiguities. The user-agent decides what to do. Very much this. How, when and for how long a browser caches is first and foremost a UI/UX question. The browser should act as the user expects, and may work to change those expectations (i.e a specialized browser that behaves in a very specific manner may describe its usage case and consequences in documentation). Us authors have little control over how our content is fetched, displayed, or otherwise consumed. On an Amfora-related note: makeworld talked about the caching on IRC the other day, and another user brought up that it seemed like Amfora presented cached content when a previously-visited link was clicked. Makeworld commented that this was unintended, and said they would fix it for a later release. (At least that?s how I remember it; maybe makeworld can weigh in.) Cheers, ew0k Sent from my smart speaker
---
Previous in thread (9 of 13): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)
Next in thread (11 of 13): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)