Does Cosmos handle a 31 permanent redirect of previous gemtext feed links that aggregated before? I updated my capsule to status 31 redirect from an ambiguous path to the specific file it's serving in an attempt to make my paths less ambiguous to help with offline support. My page gemini://vigrey.com/journal now 31 redirects to gemini://vigrey.com/journal/index.gmi and doesn't seem to aggregate into Cosmos anymore. It's fine and not the end of the world by any means if that means it won't be aggregated into Cosmos anymore, but was still curious if it is an issue.

vigrey.com/journal

vigrey.com/journal/index.gmi

Posted in: s/Cosmos

☀️ vi

Feb 01 · 4 months ago

2 Comments ↓

🕹️ skyjake [mod...] · Feb 01 at 13:03:

While Cosmos should follow redirects when checking posts, it does not keep individual feed indices apart from the primary source aggregators.

So you'll need to submit your updated links/feeds to Antenna or get it picked up via another aggregator that Cosmos keeps track of.

🍵 michaelnordmeyer · Feb 02 at 15:55:

By changing the feed URL user's browsers have lost the read state of all the links in the feed, because /journal and /journal/index.gmi are different URLs.

Additionally, the server redirects vigrey.com to vigrey.com/index.gmi. Two requests for one page to load, because nobody will add index.gmi when typing your domain name.

And if I go up from /journal/index.gmi by using a shortcut or the browser's menu button, I get another redirect from / to /index.gmi.