@mckinley@twtxt.net @lyse@lyse.isobeef.org The link rel bit is because the feed can have relative urls. ie, if it is on http://example.com/feed, in can have somewhere in there a
for eg.. If I download that feed I to my hard-drive and then try to render it, I need to know that “icon.jpg” is relative to http://example.com/feed, ie, that I will find it at http://example.com/icon.jpg (and not locally, next to the feed file I downloaded).
I hope my explanation makes sense…
@marado@twtxt.net As far as I can tell, the spec only provides relative link resolution through the xml:base attribute.
Any element defined by this specification MAY have an xml:base attribute…When xml:base is used in an Atom Document, it [establishes] the base URI (or IRI) for resolving any relative references found within the effective scope of the xml:base attribute.
This is all it has to say on rel="self":
The value “self” signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.
Unfortunately, the reasoning behind rel=“self” remains a mystery.
I don’t know where it would be useful, either. I have one in each of my Atom feeds for the same reason. It’s a Chesterton’s Fence situation for me. It’s not doing any harm, and the W3C says it should be there, so I put it there.
@lyse@lyse.isobeef.org Yeah I dumped my cache to have a look 🤦♂️ Somehow someone or another has followed / fetched your archived feeds and those Twters are now cached 😢
I fixed one case already but this is different 😅
Looking into it… 👀
@lyse@lyse.isobeef.org After this commit:
* 0d751800 2022-11-11 | Add FeatureFixCachedTwtersForArchivedFeeds (fix_cached_twters_for_archived_feeds) to avoid caching Twter objects for Archived Feeds (HEAD -> filter_and_lists, origin/filter_and_lists) [James Mills]
And blacklisting ^lyse\.isobeef\.org$ (because I couldn’t figure out how to go fix broken/bad Followings of Users on my pod easily) there should only be two Twter objects for you now, @lyse@lyse.isobeef.org and @lyse-backup@twtxt.net (as expected).
Hopefully we don’t run into any other weird edge cases 😅
@lyse@lyse.isobeef.org No it’s not right but as I said on IRC I haven’t figured out a way to handle bad Following yet 🤣