💾 Archived View for station.martinrue.com › sirwilburthefirst › dc02b7d240604e3c9f10be652cc05bfa captured on 2023-07-22 at 18:05:30. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-05-24)
-=-=-=-=-=-=-
Spartan Should Not Use text/gemini
gemini://space.matthewphillips.info/posts/spartan-gemtext/
1 year ago · 👍 skyjake, axion, krixano, arman
[1] gemini://space.matthewphillips.info/posts/spartan-gemtext/
This smells like the "every Lisp language occupies the .lisp file extension and the text/lisp" prolem (i.e. it's not /really/ a problem in my opinion). · 1 year ago
Although I am unfamiliar with Spartan, I strongly agree with your stance 💪 · 1 year ago
I too hope @mozz can clarify... My thinking is that either =: is not supported (gemini) and will simply show as text, or it is supported by browser and the server/cgi at the URL provided. At worst, you see that it's a weird dead link and upgrade/switch browsers; no harm done.
Much like _no highlights_ are supported by gemtext, but should someone render the text above as highlighted, no harm done. · 1 year ago
Maybe @mozz can explain the reasoning here? Certainly would be less ambiguous to have a unique MIME type "text/spartan", even if it just duplicates text/gemini and adds one line type. · 1 year ago