# 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 15
# self = https://watcher.sour.is/conv/vw3qicq
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.
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.
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.
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.
@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.)
@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.)
@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.)
@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.
@lyse That’s smart. Fewer features, fewer breakage. 😏
@lyse That’s smart. Fewer features, fewer breakage. 😏
@lyse That’s smart. Fewer features, fewer breakage. 😏
@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.