# 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/cladbla
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔
It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.
Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔
It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.
Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔
It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.
Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔
It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.
Hmm. 🤔
@movq This is gone though right? 🤔
@movq This is gone though right? 🤔
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟