# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 6
# self = https://watcher.sour.is/conv/yxsa4oa
@mckinley Interesting, the URL https://mckinley.cc/notes/20221102-no-search.html indicates it was published on 2nd of November, but the page itself says it was already done on the 1st. To confuse myself even more, Newsboat renders the timestamp in my local timezone, making it even the 3rd. So I reckon just the page timestamp is off. :-)
@lyse In the atom feed I can see that the feed itself was updated on "2022-11-02T22:54:53-07:00" which is the same as the last notes post.
His RSS feed is also a bit outdated despite saying he will updated it. But maybe it would be better to get rid of it at all? I am not sure if mine works 100% correct. But should be.
I do like the XSLT Stylesheet though. I think I will implement something for my site as well.
@carsten Yeah, I reckon only the date on the page claiming the 1st is wrong. The Last-Modified HTTP response header of the HTML page is even a tad behind, indicating another quick fix, such as correcting a typo or something. But that's totally fine. And in a few days nobody cares about exact days anymore anyways. Was it a week or month before or after? Just doesn't matter. I thought it was just interesting to see three different dates on my end. ;-)
I haven't noticed any anomalies with the Atom feed, but he switched from RSS to Atom a few weeks ago. So I don't follow the old RSS feed anymore.
@eaplmx Oh yes, time is fun. ;-) Certainly have to look at your links in more detail later.
@lyse You're right, I copied the last note for the boilerplate and I forgot to change the date. It's fixed now.
The Last-Modified header probably accounts for the time it took in between setting the timestamp in the Atom feed and pushing the changes to the Web server.
@carsten, what's wrong with the RSS feed?
@mckinley Ah, makes sense. Yeah, publishing is often not as instant as one thinks. :-)