# 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 14
# self = https://watcher.sour.is/conv/apjuyca
And there it is: Another rotation of this feed.
(Yeah, 100 lines is quite low.)
I bet you guys already implemented retrieving archived feeds! :-)
And there it is: Another rotation of this feed.
(Yeah, 100 lines is quite low.)
I bet you guys already implemented retrieving archived feeds! :-)
And there it is: Another rotation of this feed.
(Yeah, 100 lines is quite low.)
I bet you guys already implemented retrieving archived feeds! :-)
@movq you are going to have, pretty soon, hundreds upon hundreds of tiny files laying around! I don't think Yarn fetches archived files, but keep archives of old twts. That, and the cache should work.
@fastidious Yes, it’s too low. I guess I’ll still keep it that way for a little while longer, just to make sure that the code works as expected. :-) Maybe some new corner cases show up. But eventually, I’ll increase the threshold.
@fastidious Yes, it’s too low. I guess I’ll still keep it that way for a little while longer, just to make sure that the code works as expected. :-) Maybe some new corner cases show up. But eventually, I’ll increase the threshold.
@fastidious Yes, it’s too low. I guess I’ll still keep it that way for a little while longer, just to make sure that the code works as expected. :-) Maybe some new corner cases show up. But eventually, I’ll increase the threshold.
I see your feed has a prev on the header, but older feeds do not have a next. If browsing to older feeds is to be possible, how does one handles the browsing from the oldest, to the next, to the next, and so on? If I am browsing twtxt-old_2021-12-23_f6y65bq.txt, how do I know which is the next newer (but not the newest)?
@fastidious You don’t. A next field was discussed in the original draft, but then it was discarded. It’s easier to implement without it and you don’t really need it for *automated* feed retrieval. For manual retrieval, though, it would have been helpful.
It was probably discussed in the pull request – or in some twtxt thread, which I can’t find anymore. 🥴
@fastidious You don’t. A next field was discussed in the original draft, but then it was discarded. It’s easier to implement without it and you don’t really need it for *automated* feed retrieval. For manual retrieval, though, it would have been helpful.
It was probably discussed in the pull request – or in some twtxt thread, which I can’t find anymore. 🥴
@fastidious You don’t. A next field was discussed in the original draft, but then it was discarded. It’s easier to implement without it and you don’t really need it for *automated* feed retrieval. For manual retrieval, though, it would have been helpful.
It was probably discussed in the pull request – or in some twtxt thread, which I can’t find anymore. 🥴
@movq Nope haven't yet sorry 🤣
@movq Nope haven't yet sorry 🤣
@movq Of course I did! Not. :-/