[Spec] Spec (un)freezes and the spec's future

[Luke Emmet]

On 22-Dec-2020 18:56, Simon wrote:
>
>> The general problem is we cannot know which are sensitive URLs and 
>> which are not. 
>
> Then we agree on that !
>
> I just wanted to show that we are easily thinking gemini input as HTTP 
> GET parameters, but they aren't, even if they are passed in the URL. 
> The only way to not deal with this server side problem, would be to 
> not log any input.

Except - au contraire - they are indeed very like HTTP GET parameters, 
ticking the same boxes just like HTTP

[x] part of the URL syntax
[x] linked to a client UI behaviour
[x] opaque, server-specific semantics
[x] replayable when the link is shared elsewhere
[x] largely indistinguishable from other elements of the URL submitted 
to the server (e.g. host/foo/bar ~ host/foo?bar)

I know the web is officially persona-non-grata round these parts, but 
URL semantics are more or less common when using them for a distributed 
hypertext system of webspace or geminispace

Regards

  - Luke