💾 Archived View for station.martinrue.com › justyb › b3109dcbdd7943129531362023bf849b captured on 2023-01-29 at 19:51:19. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
Clear example of the difference between mindset of web browser devs and Geminispace devs.
I don't want to encourage the use of Markdown instead of Gemtext, as that would make viewing content in other clients a worse experience.
gemini://skyjake.fi/gemlog/2022-05_lagrange-1.13.gmi
Had this been the web, a browser dev would have been "Cool! Now we can crush everyone else!" @skyjake actually stopping to think about other clients' devs is something you just don't see on the web anymore.
9 months ago · 👍 quien, oofbar, eph, schnouki, haze, gnuserland
[1] gemini://skyjake.fi/gemlog/2022-05_lagrange-1.13.gmi
@dimkr Spartan (and Gopher) are distinct from Geminispace, even though they are under the same "small internet" umbrella. People should have the choice to use whatever protocol suits them best. In other words, nobody should be "pressured" to use Gemini if they prefer something else.
The problem with Markdown is that it can fragment Geminispace. It's a superset of Gemtext so people may prefer to have its additional markup features, but that goes against the common convention that content is served as 'text/gemini' that all clients can parse/show equally well. · 9 months ago
Isn't Spartan support a good counter-example? If parts of Geminispace transition to Spartan and only some browser(s) support the other protocol natively ... · 9 months ago
I like this! It avoids the “best viewed with certain-browser” problem pretty neatly.
(however, I am a little hypocritical as I have “best viewed with Lagrange” at the bottom of my gemlog 😜) · 9 months ago