💾 Archived View for station.martinrue.com › sirwilburthefirst › dc02b7d240604e3c9f10be652cc05bfa captured on 2023-04-26 at 14:47:09. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-04-20)

➡️ Next capture (2023-05-24)

🚧 View Differences

-=-=-=-=-=-=-

👽 sirwilburthefirst

Spartan Should Not Use text/gemini

gemini://space.matthewphillips.info/posts/spartan-gemtext/

11 months ago · 👍 skyjake, axion, krixano, arman

Links

[1] gemini://space.matthewphillips.info/posts/spartan-gemtext/

Actions

👋 Join Station

4 Replies

👽 isoraqathedh

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). · 11 months ago

👽 arman

Although I am unfamiliar with Spartan, I strongly agree with your stance 💪 · 11 months ago

👽 stacksmith

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. · 11 months ago

👽 skyjake

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. · 11 months ago