-- Leo's gemini proxy
-- Connecting to gem.acdw.net:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini; charset=UTF-8
I love this idea, and I'm glad most seem to be following it. One quibble, however, is in "round-up" posts such as the one I'm currently writing (and you, presumably, are currently reading): there's a lot of backlinks here, with a lot of replies. What do? As you can see, I just separate everything by headers, and hope for the best.
P.S. One thing that /would/ be nice is some sort of section separator in gemtext. I personally like `---`, though `^L` (ASCII Form Feed) has been suggested and I think would also suffice.[a]
I also love this idea, and will implement it going forward! An alternative could be using the ~fancy~ bois, like *, †, ‡, §, ‖, ¶, #, Δ, ◊, ↓, ☞, or even ※.
Great point using `sed'! Here's a corrected "polished script:"
#!/bin/bash
url="$1"
serv="${url##*//}"
serv="${serv%%/*}"
port="${url#*:}"
port="${port%%/*}"
port="${port:-1965}"
printf '%s\r\n' "$url" |\
openssl s_client -quiet -connect "$serv:$port" |\
sed 1d |\
mpv --cache-secs=10 -
Also, I want to reply to the "pipe to image viewer" idea. My dream Gemini browsing experience would feature an auto-call-out to image viewers/music players/etc., in a non-blocking manner, so that you could click on an image and scroll and then it'd pop up next to the browser window, then you could look at it and close it out. Real one-thing-well-type feel.
[a] One thinks of "Fire and Ice," by Frost:
Some say the world will end in fire, Some say in ice. From what I’ve tasted of desire I hold with those who favor fire. But if it had to perish twice, I think I know enough of hate To say that for destruction ice Is also great And would suffice.
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Copyright (c) 2019-2020 Case Duckworth. CC-BY-SA.
-- Response ended
-- Page fetched on Fri May 3 00:34:43 2024