Caching and status codes
John Cowan
cowan at ccil.org
Sat Nov 7 22:48:33 GMT 2020
On Sat, Nov 7, 2020 at 2:35 PM <khuxkm at tilde.team> wrote:
> Again, your elitism is showing. I feel like adding a way to signal
> whether or not you can safely cache a response isn't really sacrificing
> any of the Gemini ethos: simplicity, privacy, or generality.
>
+1
> I fail to see how adding "safe to cache" and "do not cache" status codes
> would make using netcat different from Kristall or any other client. Just
> treat it as a 2x success status code, and move on.
>
In addition, if you click on a link saying "Random cool picture!", first of
all that's safe (no pixel bug in it), and second, if you notice that it's
the same picture as last time, you do a refresh, causing your client to
override its cache, and you see a different picture. Everybody wins.
John Cowan http://vrici.lojban.org/~cowan cowan at ccil.org
There is no real going back. Though I may come to the Shire, it will
not seem the same; for I shall not be the same. I am wounded with
knife, sting, and tooth, and a long burden. Where shall I find rest?
--Frodo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201107/6ba6a604/attachment-0001.htm>
More information about the Gemini
mailing list