paritybit.ca

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

commit f7e16418307c650db3fb12b3e3a864e1baff1be3
parent 2b061781791b6931e866ac79febbc4704ab7c0a9
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Mon,  2 Nov 2020 03:45:02 -0500

Minor tweaks to most recent blog post

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

diff --git a/gemini/pages/blog/gemini-is-up-and-running.gmi b/gemini/pages/blog/gemini-is-up-and-running.gmi @@ -2,11 +2,11 @@ Written By: Jake Bauer | Posted: 2020-11-02 | Last Updated: 2020-11-02 -The Gemini protocol is a new "small Internet" protocol which aims to sit in between Gopher and the HTTP-based Web in terms of functionality. I previously wrote a bit about it and you can find a nice quick breakdown in this [blog post on Drew DeVault's blog. +The Gemini protocol is a new "small Internet" protocol which aims to sit in between Gopher and the HTTP-based Web in terms of functionality. I previously wrote a bit about it and you can find a nice quick breakdown in a blog post on Drew DeVault's blog linked below. => https://gemini.circumlunar.space The Gemini protocol main page => https://www.paritybit.ca/blog/diving-deeper-into-the-small-internet My previous blog post -=> https://drewdevault.com/2020/11/01/What-is-Gemini-anyway.html Drew DeVault's blog post +=> gemini://drewdevault.com/2020/11/01/What-is-Gemini-anyway.gmi Drew DeVault's blog post When I wrote that first blog post about Gemini and the small Internet, I got a quick and dirty Gemini server set up which mirrored what I had created for Gopher. That whole situation was a little bit clunky and I didn't have a good way to maintain it in the long run, so I instead decided to scrap that and start over. Having ditched Gopher (because I don't really see a reason to run it alongside Gemini), I now run only Gemini and HTTP sites. @@ -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 HTTP 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 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. 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,7 +35,7 @@ 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 HTTP pages over to +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