Søren Peter Mørch

Conversation

Recent twts in reply to #vw3qicq

movq@www.uninformativ.de
Hey @sorenpeter, I’m sorry to tell you, but the prev field in your feed’s headers is invalid. 😅

First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.

For reference, the prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
1 week ago
sorenpeter@darch.dk
Hi @movq, is it better now?
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.
In reply to: #vw3qicq 1 week ago
movq@www.uninformativ.de
@sorenpeter Yes, that’s better, thanks! 👍

My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃

Oh, I forgot to mention: The URL should be relative to the fields location, so it should be prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
In reply to: #vw3qicq 1 week ago
lyse@lyse.isobeef.org
@movq My setup hasn't changed or progressed for over a year. I still don't consume archive feeds, just produce one every now and then.
In reply to: #vw3qicq 1 week ago
movq@www.uninformativ.de
@lyse That’s smart. Fewer features, fewer breakage. 😏
In reply to: #vw3qicq 1 week ago
lyse@lyse.isobeef.org
@movq Exactly! :-D Or call it lazy in that case, to be honest. I just got used to all my workarounds in place. :-/ I still want to recreate tt2 one day. I started with it months ago and never touched it since. Too much other stuff going on.
In reply to: #vw3qicq 1 week ago
Comment via email