# 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 9
# self = https://watcher.sour.is/conv/3iiq7aq
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
I mean bug where jenny don't know about these id's and tried to request from twtxt.net (prologic sent access logs)
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?