content-disposition vs data URI

On 6/4/20 3:58 PM, Petite Abeille wrote:
> On the server side, I presume?
> 
> What happened to the notion of client's agency?
> 
> 5.3.2 Link lines/Clients can present links to users in whatever fashion
> the client author wishes./

The clients can present _links_ to users in whatever fashion. They
should still be links. If a URL pattern allows for the encoding of
random material, that should not be license to inline content. The goals
of the project are clear philosophically that text/gemini represents a
single document format that can hyperlink. Pulling in data in the ways
you are describing is no different from the earlier suggestion of a <=
line or frames.

If your client wants to display images inline in the document AFTER a
user clicks on a link, that would be within the purview of a client
author. A client should not choose to inline images automatically,
though, as they would no longer be links.

I think this idea, not the specific technical parts, but the theory and
philosophy, should answer all of the ideas you've been presenting
regarding URL hackery collectively in the negative.

---

Previous in thread (3 of 6): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)

Next in thread (5 of 6): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)

View entire thread.