💾 Archived View for caseyrichins.online › logs › 2022-11-13_fixed-atom-feed.gmi captured on 2023-06-14 at 13:53:19. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
Published November 13, 2022
I've been having a very weird issue with my atom feed not updating properly in amfora. It was driving my crazy because i had no way to get any log of what was going on that I could use for troubleshooting. Today I took the time to go through the issue once more and I'm happy to report that my feed is now updating properly in the amfora browser. The short story of the was that in the code for that atom.xml file I set the href ref value to be "alternative" instead of "alternate". How I had missed that I was not certain. I had keep thinking that it had something to do with the timestamps perhaps and had tried various things trying to get it work. The feed was working the entire time in Lagrange but not in amfora.
My first thing trying this morning was to search if anyone else had had this issue. I was looking for anything that would give me a clue, not finding one I visited the amfora documentation page about subscriptions.json (see Footnotes). On the documentation was the location of the file that is used to manage subscriptions, it is located in ~/.local/share/amfora/subscriptions.json and contains all of the subscriptions that you've subscribed to. Below is the file that was on my computer prior to making the fix. You'll notice that the newest three entries are missing a links section. So this became my first clue to determine what as happening.
"items": [
{
"title": "Twitter and social media accounts",
"updated": "2022-11-07T00:00:00Z",
"updatedParsed": "2022-11-07T00:00:00Z",
"published": "2022-11-07T00:00:00Z",
"publishedParsed": "2022-11-07T00:00:00Z",
"guid": "gemini://caseyrichins.online/logs/2022-11-07_twitter.gmi"
},
{
"title": "Goodbye Ego",
"updated": "2022-09-17T00:00:00Z",
"updatedParsed": "2022-09-17T00:00:00Z",
"published": "2022-09-17T00:00:00Z",
"publishedParsed": "2022-09-17T00:00:00Z",
"guid": "gemini://caseyrichins.online/logs/2022-09-17_Goodbye-ego.gmi"
},
{
"title": "Capsule Updates for Sept 2022",
"updated": "2022-09-01T00:00:00Z",
"updatedParsed": "2022-09-01T00:00:00Z",
"published": "2022-09-01T00:00:00Z",
"publishedParsed": "2022-09-01T00:00:00Z",
"guid": "gemini://caseyrichins.online/logs/2022-09-01_Sept-Updates.gmi"
},
{
"title": "Where your fear is, there lies your task",
"links": [
"gemini://caseyrichins.online/logs/2022-08-08_Fear.gmi"
],
"updated": "2022-08-08T00:00:00Z",
"updatedParsed": "2022-08-08T00:00:00Z",
"published": "2022-08-08T00:00:00Z",
"publishedParsed": "2022-08-08T00:00:00Z",
"guid": "gemini://caseyrichins.online/logs/2022-08-08_Fear.gmi"
},
Looking at the atom file itself I was presented the following glaringly obvious answer that I had missed numerous times before which you see from the patch entry below. Once I fixed the rel value and rebuilt my docker image, pushed to docker hub and pulled down on my host followed by a compose up command to recreate the container I was presented with an updated subscriptions page in amfora upon opening for the first time.
- <link href="gemini://caseyrichins.online/logs/2022-09-17_Goodbye-ego.gmi" rel="alternative"/> + <link href="gemini://caseyrichins.online/logs/2022-09-17_Goodbye-ego.gmi" rel="alternate"/>
I'm not certain as to why Lagrange had no issues with the feed, but at least it was working so I knew my feed was working.
My next task is to figure out why my pages are not indexing properly on geminispace.info, my atom feed is there but the if I search for entries related to my domain the pages don't show up. I've also been trying to locate the one page that I found which I thought I had bookmarked that contained a patch for Mollybrown to allow it to be bound to a socket or localhost to host behind a proxy for load balancing and linear scaling of gemini capsules.
-------------------