paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit d310ced348827c1df87c57e9814d5c124f248f36
parent f7e16418307c650db3fb12b3e3a864e1baff1be3
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Mon,  2 Nov 2020 03:47:25 -0500

Minor tweaks to most recent blog post

Diffstat:
Mgemini/pages/blog/gemini-is-up-and-running.gmi | 2+-
Mhttp/pages/blog/gemini-is-up-and-running.md | 13+++++++------
2 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/gemini/pages/blog/gemini-is-up-and-running.gmi b/gemini/pages/blog/gemini-is-up-and-running.gmi @@ -15,7 +15,7 @@ I am now running the gmnisrv Gemini server and maintain a `gemini/` folder along => https://git.sr.ht/~sircmpwn/gmnisrv The gmnisrv repository => https://git.sr.ht/~jbauer/paritybit.ca This site's repository -I also briefly experimented with converting some of these HTML pages over to Gemini so one could get a perfectly mirrored copy of what is available here over on Gemini. Unfortunately, that resulted in pages which were clunky, messy, and resulted in a degraded Gemini experience. I came to the conclusion that text hosted on Gemini should be written in gemtext and explicitly tailored to the constraints of that platform rather than trying to fit the square peg of made-for-HTTP content into the round hole of Gemini. +I also briefly experimented with converting all of these HTML pages over to Gemini so one could get a perfectly mirrored copy of what is available here over on Gemini. Unfortunately, because it was scripted, that resulted in pages which were clunky, messy, and ultimately lead to a degraded experience viewing this site using Gemini. I came to the conclusion that text hosted on Gemini should be written in gemtext and explicitly tailored to the constraints of that platform rather than trying to fit the square peg of made-for-HTTP content into the round hole of Gemini. Blog posts written for this site will also be made available on Gemini, as will any other pages. A Gemini-specific Atom feed will also be appearing soon. I suppose it's also fitting that this is my final blog post for #100DaysToOffload: ending an era of HTTP-only blog posts whilst beginning an era of content on two protocols. I have very much enjoyed this challenge and look forward to continuing to write more. diff --git a/http/pages/blog/gemini-is-up-and-running.md b/http/pages/blog/gemini-is-up-and-running.md @@ -35,13 +35,14 @@ server and maintain a `gemini/` folder alongside an `http/` folder in my gmnisrv because of its simple implementation (minimal dependencies, low LoC count, etc.). -I also briefly experimented with converting some of these HTML pages over to +I also briefly experimented with converting all of these HTML pages over to Gemini so one could get a perfectly mirrored copy of what is available here over -on Gemini. Unfortunately, that resulted in pages which were clunky, messy, and -resulted in a degraded Gemini experience. I came to the conclusion that text -hosted on Gemini should be written in gemtext and explicitly tailored to the -constraints of that platform rather than trying to fit the square peg of -made-for-HTTP content into the round hole of Gemini. +on Gemini. Unfortunately, because it was scripted, that resulted in pages which +were clunky, messy, and ultimately lead to a degraded experience viewing this +site using Gemini. I came to the conclusion that text hosted on Gemini should be +written in gemtext and explicitly tailored to the constraints of that platform +rather than trying to fit the square peg of made-for-HTTP content into the round +hole of Gemini. Blog posts written for this site will also be made available on Gemini, as will any other pages. A Gemini-specific Atom feed will also be appearing soon. I