💾 Archived View for rawtext.club › ~sloum › geminilist › 006135.gmi captured on 2024-03-21 at 16:32:39. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
PJ vM pjvm742 at disroot.org
Tue Mar 16 12:40:27 GMT 2021
- - - - - - - - - - - - - - - - - - -
On 16/03/2021 02:18, Luke Emmet wrote:
the user may not be able to readily actually see the location, which
may be a security concern in its own right.
The hidden part of the URI would always be something that the user typedin a short while ago. Also, unless one holds your view that a URI mustcontain only location information (in that view SC11 is invalid), in thecase of SC11 the query would not really be considered part of the location.
Ironically the gemini URI scheme does not permit users to put user
info (user name or password) into the URI.
Allowing both the userinfo component and the query component would meantwo different methods for input/parametrisation, one of which cancontain one string and one of which can contain either one or two, andthey could potentially both be used in one URI. For consistency's andsimplicity's sake, allowing only the query component and not theuserinfo component is a logical choice.
So no I won't be attempting to obfuscate URIs in GemiNaut and it
will warn users if the server invites them to put sensitive info into
the URI.Do as you wish with your client.
-- pjvm