4 ms·
Using HTML over HTTP in any form opens you to tracking, through the referer header, ETag lookup, and cookies. The idea behind Gemini is to cut off all such cap
by nine_k 6y ago
Using HTML over HTTP in any form opens you to tracking, through the referer header, ETag lookup, and cookies.
The idea behind Gemini is to cut off all such capabilities (even when useful for good things) and prevent attempts to add them as extensions. This may make sense in the niche they are targeting.
This also prevents common session tracking mechanisms, but even form submission is not a thing in Gemini anyway.
- zzo38computer 6y agoIt won't prevent serving HTML with GET forms (although POST forms won't work, and neither will cookies), although a client may very well not understand the document (or any other HTML document) and not display it (and even if it does understand HTML, it might restrict HTML with Gemini by default, in order to avoid tricking the user into thinking that one kind of document is a different kind, and/or in order to avoid doing things which are undesirable with Gemini; HTML is probably mostly undesirable with Gemini anyways). If you need an interactive system, then SSH or Telnet might be better, rather than Gemini or HTTP(S). For other things, other protocols will be better, e.g. for communications, IRC or NNTP would help (depending on the kinds of communications). They also mentioned a Titan protocol, for writing to Gemini files.
- nine_k 6y agoI suppose that as the Gemini network grows, someone will create a search engine. The old-school "?foo+bar" style of GET queries should be enough even on clients supporting only standard Gemini markup. (Arbitrary MIME types are supported, so enhanced or entirely different interfaces are possible.)
- Seirdy 6y agoIt already has one: GUS. A live instance is running at gemini://geminispace.info with a good index.
- zzo38computer 6y agoYes, and that is independent of the MIME type; there is a response code to specify that input is required.