> clients MUST NOT automatically make any network connections as part of displaying links whose scheme corresponds to a network protocol (e.g. links beginning with gemini://, gopher://, https://, ftp:// , etc.).
I'm aware, I meant inline images in an HTML mirror.
Looks like this might not be exactly what I'm looking for though. It's an HTTP to Gemini proxy, I'm looking for a Gemini to HTTP proxy, I want Gemini to be a first class citizen. The only reason I want to be able to deliver over HTTP is in the event someone doesn't want to mess with Gemini, but Gemini will come first for me.
On a related note, it seems strange that I can't access sr.ht content over gemini. I know that it's not quite trivial to render something suitable if you're starting with DHTML (lol) but it seems like srcmpwn would be the kind of person to bother doing it.
It's not OK in the sense that it is a spec violation, at least. Some clients have images that load in-line on mouseover or click, which isn't a spec violation. You could do that with HTML.
If people specifically sought out your client because it automatically renders images inline, who could be bothered to get upset about a "spec violation"? The author of Gemini? What would he be able to do?
Probably someone would submit a PR complaining. A lot of folks in the gemini community are strict about the spec. In my view, they would be justified in doing so — I think adherence to specs is important in any domain, not just gemini.
Drew himself threatened to block a Gemini agent that fetched /favicon.png on every page load. I tend to agree with the idea that Gemini should not be extended, as there's always HTTP+HTML for that.
I kind of agree with him, despite being of the opinion that optional inline images should be allowed by the spec. Fetching favicons is going a bit too far for my tastes.
I definitely see situations where Gemini wants to be as bandwidth-friendly as possible, and certain clients auto-downloading resources from the same server would make it difficult to estimate costs/resources/etc.
However for external images available over http/s, I think that should be up to the client.
Inline images is a violation of the Gemini spec:
> clients MUST NOT automatically make any network connections as part of displaying links whose scheme corresponds to a network protocol (e.g. links beginning with gemini://, gopher://, https://, ftp:// , etc.).