You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now that, in the I4kFindSymbols, !&+# have the same level, and function (it seems) as the new "protocol symbols" (they all end up by a :, as the new URL(window.location).protocol has), gopher:, git:, finger: etc.
how should they handle a "Find query"? new URL(<protocol_scheme_other_than_http>) might not give detail on the URI parsing
by default we're in a web browser (first used case), and trying to resolve the user request, even though the browser does not support this (but some remote/local web-URL might be able to proxy them for us, if we build the proxy_app + protocol path correctly)
gemini:hello world
gemini: hello world
gemini: hello world
gemini:!d hello world
gemini:!m tokyo
gemini:+capsule hello world
gemini:&network username capsule-id
gemini://my-gemini-capsule.example.org/some/path
now that, in the
I4kFindSymbols
,!&+#
have the same level, and function (it seems) as the new "protocol symbols" (they all end up by a:
, as thenew URL(window.location).protocol
has),gopher:
,git:
,finger:
etc.new URL(<protocol_scheme_other_than_http>)
might not give detail on the URI parsingOr more generally (pseudo https://en.wikipedia.org/wiki/Web_Ontology_Language)
The text was updated successfully, but these errors were encountered: