[tech] Questions about cache

[Stephen]

Gemini spec does not mention caching, and the FAQ says:

 > Gemini has no support for caching

So I was a bit surprised when I was putting together some dynamic 
content for my capsule and found that my client (amfora) was caching 
things. I was able to get around it by using temporary redirects to add 
cache busting query strings.

I don't have much experience with gopher, but I have seen that this has 
been a problem in the gopherspace. On the mozz.us phlog entry for his 
Rock Paper Scissors game he notes:

 > The random token at the end of the URL (e.g "/bfhqK3kH") doesn't
 > actually represent anything. I only added it for cache-busting on
 > lynx (otherwise you would always see the same result as the first
 > time you loaded the page). I really hate doing that because it screws
 > with the purity of my gopher routes. But a lot of people (including
 > myself) use lynx. It sort of reminds me of JS hacking to support old
 > Internet Explorer versions.

( gopher://mozz.us:70/1/phlog 2019-04-12 )

Is there some guarantee that a capsule writer has on what may _not_ be 
cached, or is it entirely up to the client's discretion? If the latter, 
is this something which could be clarified in the spec? My impression 
from this ML was that caching is frowned upon (except for perhaps 
navigating back and forth through your history), but this has not been 
my experience (at least with amfora).

~Stephen ( gemini://drsudo.com/ )