 |
AVOIDING THE GRAVITY-WELL OF WEBBINESS IN GOPHER |
|
|
|
A response to |
 |
Pondering what's inbetween Gopher and the web |
|
|
|
With regard to formats: |
|
|
|
The author suggests that the 'default format' should not be 'plaintext' but a … |
|
|
|
Any markup format that supports more features than just links is a waste, part… |
|
|
|
The primary feature that the author suggests as a driver for this format chang… |
|
|
|
With regard to TLS: |
|
|
|
I'm not sure whether or not encryption for gopher makes sense. Gopher is mostl… |
|
|
|
Now, TLS doesn't protect the bits of information that maybe might be sensitive… |
|
|
|
Right now, nobody pays much attention to gopher traffic. If they start, it wil… |
|
|
|
We know what happened when the web got crypto support: Extremely quickly, it a… |
|
|
|
My take on how to encrypt gopher is: Gopher itself remains plain-text, but enc… |
|
|
|
In general: |
|
|
|
Folks only bother to use gopher because the web's design philosophy doesn't su… |
|
|
|
Gopher is pragmatic in a different way: it does not favor what can be incremen… |
|
|
|
Gopher is the forth of internet protocols not because the user community is th… |
|
|
|
This makes it harder for folks to unilaterally add features that users don't n… |
