Caching and sizes, the explosion of responise codes (was Re: Caching and status codes)

Zach DeCook <zachdecook at librem.one> writes:

> A "please don't cache" response code would be (ab)used by servers who
> desire to track their users.

I think this is an important point which has been largely overlooked. We
do not have (many?) bad actors on the gemiverse for now, but this can't
continue forever.

I'm also wondering whether we shouldn't state outright that Gemini
requests are expected to be idempotent. I know this would break dynamic
pages that people are already using and enjoying (astrobotany,
guestbooks), but other types of dynamic pages with user input would
still be relevant, like searches and local weather.

I dislike the idea of adding caching-related result codes. That's one of
the things that drove the increasing complexification of HTTP during the
HTTP/1.0 era (i.e., before HTTP/1.1). If we're not doing full-fledged
application development on top of Gemini, we don't need server-side
cache control.

-- 
+-----------------------------------------------------------+
| Jason F. McBrayer                    jmcbray at carcosa.net  |
| A flower falls, even though we love it; and a weed grows, |
| even though we do not love it.            -- Dogen        |

---

Previous in thread (49 of 55): 🗣️ Ali Fardan (raiz (a) stellarbound.space)

Next in thread (51 of 55): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)

View entire thread.