Phlog Revamp and Response to Solderpunk I'm considering a revamp of my phlog much as logout did recently[0], with a main gophermap and a simple listing of all posts for all years on one page. It's certainly possible to to this and preserve the original links, since the gophermap gives you one level of indirection (except for slerm links, which I would just leave online after converting). Also, when I go back and view my phlog archives at SDF [1], I see that from 2009 to 2018 (when I moved it to circumlunar.space) I only averaged about one post a month. We're talking a tiny-sized gophermap compared to what gets downloaded to your client on any modern website, and as logout notes having meaningful selectors helps index your posts in Veronica [2]. I mentioned this before as well [3], I think it would be useful for anyone who has a phlog and wants it indexed to use meaningful selectors (or filenames if you don't use a gophermap). And having meaningful selectors probably alleviates the need to manage post summaries in your gophermap, since you can just skim a list of selectors to see what might interest you. This also appeals to me as it encourages simple, deliberate phlogging. Step one - write some text and save it in /phlog directory. Step two - add a line to the gophermap to link to new file. If you phlog infrequently this can be done manually, but it is the basis for the mkgopherentry and my own phlogit [4] tools, the latter I still use for my French language phlog [5], which I note with some chagrin I also do not update frequently and could certainly be managed manually. Solderpunk had some interesting thoughts on gopher [6]. I am of course 100% behind SSL-enabled gopher sites. The alternative is the web-to-gopher proxy over SSL, tilde.team does this for user's gopherholes [7], which of course works fine but is not gopher at all. I've seen some people advocate using port 7070 for SSL/gopher, and some port 7443, I would only add that it would be better for security reasons to use a privileged port (< 1024) to prevent users from being able to run their own servers, especially if using a TOFU-based system. There are plenty of unassigned, privileged port numbers available for this. As far as text formatting, I am ambivalent. I don't feel the need personally to use a text markup language, apart from an occasional use of _underscores_ or *asterisks* for emphasis, and of course the now-ubiquitous bracketed link references. That said I don't think adding a selector for such a markup hurts anything and it can be simply interpreted as text by clients as a fallback. The third change sounds just like a scheme to interpret mime-types, or otherwise examine the content of a file to determine how to display or handle it. I don't think gopher needs this added complexity, it's harder for the client to fallback to a default that makes sense if they don't know the selector - should they display text, or treat the item as binary data? I just don't see a way to sensibly handle something like that without examining the file itself. [0] gopher://i-logout.cz/0/phlog/posts/2018-12-12_im_gonna_break_things.txt [1] gopher://sdf.org/1/users/slugmax [2] gopher://gopher.floodgap.com/1/v2 [3] gopher://sdf.org/0/users/slugmax/docs/gopher/making_gopher_search_useful.txt [4] gopher://sdf.org/0/users/slugmax/code/phlogit.txt [5] gopher://republic.circumlunar.space/1/~slugmax/quebec [6] gopher://zaibatsu.circumlunar.space/0/~solderpunk/phlog/pondering-whats-inbetween-gopher-and-the-web.txt [7] https://gopher.tildeverse.org/tilde.team