[SPEC] Users actions should only trigger an unique request

[Martin Keegan]

On Sat, 20 Feb 2021, Solene Rapenne wrote:

> Hi,
>
> It doesn't seem that the specification is clear that requesting
> a page shouldn't download other resources.
>
> This raises concerns and questions about inline data, currently
> in-line pictures are supported by Lagrange browser (not a default
> though).
>
> Some people noticed /favicon.txt errors in their logs, it turned out
> the Amphora client implemented an Emoji favicon support (disabled by
> default)[1] which already help tracking Amphora users. Someone made
> a ticket to ask removing this feature [2] but per the spec, it is
> not allowed or forbidden.

"Gemini interprets extensibility as a side-channel attack, and routes 
around it."

I support Solene's proposal (though I have not read the exact proposed 
wording). If the proposal is accepted into the spec, I'd also suggest that 
clients that violate it on this point be removed from the list of
Gemini clients on the main webpages. This feels uncharacteristically 
heavy-handed by my standards, but there appears no other way to stop 
Gemini being forcibly evolved in a way that damages its value to many 
users.

Mk

-- 
Martin Keegan, @mk270, https://mk.ucant.org/