181
results for "gopher"
-
I would probably place the different protocol variants of the same link listed in parenthesis either linked to gopher/gemini or perhaps by opting for an icon to depict each and then leave it to the visitor to choose. In case of video, audio and picture, in practice, the determining factor I think is usually whether the platform supports the given codec or not. I haven't seen a user browser setting for preferring codecs (or bitrates) for such elements yet.
bkil
at
2023-04-12 23:51
-
If you are linking from HTTP/HTML documents, why not also always link to HTTP/HTML documents? The target proxy of the link itself may contain the original proxied gemini/gopher link as an alternate in the `<head>` or in a HTTP header. https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel#alternate https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link
bkil
at
2023-04-12 23:46
-
specific example, use gopher links, and fallback to a gopher proxy over http
epoch
at
2023-04-12 23:40
-
it sends a "search terms" to the gopher daemon with a tab followed by the search query
prologic
at
2023-03-26 16:35
-
we think gopher is much more amenable to human-scale search than http
Soni
at
2023-03-26 16:32
-
no, gopher has search as a protocol feature
Soni
at
2023-03-26 16:15
-
no, gopher has search
Soni
at
2023-03-26 16:14
-
Isn't Gopher basicalyl just HTTP 1.0 though?
prologic
at
2023-03-26 16:13
-
in other words, raw gopher packets, with an HTTP header on top
Soni
at
2023-03-26 16:13
-
we want gopher encapsulation, not gateway
Soni
at
2023-03-26 16:13
Sort by:
Filter results by:
Tag
Query took 0s.
Search tips
- Exclusion
- +foo -bar
- Logical OR
- foo OR bar
- Exact phrase
- "foo bar"
- Partial words
- foo*
- Particular fields only
- title:foo
- domain:example.org
- nick:somebody
- after:2016-11-23
- before:2016-11-23
- date:2016-11-23