# 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 16
# self = https://watcher.sour.is/conv/3kd355q
@movq what is your cron job repeat time for jenny? Currently I have mine to every minute, and while it allows me to participate fairly quick on conversations it has some drawbacks: it captures every single edited twt, so I end up with seemingly the same twt, but not quite---as it has minor edits, etc. So, "repeats". Perhaps setting cron to check every 5 minutes or so is best?
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@quark I run the cron job every 15 minutes. Running it every minute imposes quite a bit of load on the feeds of other people. While jenny requests everything with the if-modified-since header set, not all servers honor that header. Most of all, yarn does not: https://git.mills.io/yarnsocial/yarn/issues/430
@quark … but I still get a lot of duplicate/edited twts as well. 🥴 This is one of the major drawbacks of jennys Maildir model: We never delete anything.
@quark … but I still get a lot of duplicate/edited twts as well. 🥴 This is one of the major drawbacks of jennys Maildir model: We never delete anything.
@quark … but I still get a lot of duplicate/edited twts as well. 🥴 This is one of the major drawbacks of jennys Maildir model: We never delete anything.
@movq \nFair enough, I will modify my cron job to match. When I come across edited twts, I just delete both knowing jenny will fetch the right one next iteration. I like keeping things tidy. 😊
@movq
Fair enough, I will modify my cron job to match. When I come across edited twts, I just delete both knowing jenny will fetch the right one next iteration. I like keeping things tidy. 😊
@movq Oh you mean I still haven’t fixed that bug yet! 😳 Shame in me 🤦♂️
@movq Oh you mean I still haven’t fixed that bug yet! 😳 Shame in me 🤦♂️
@prologic Yeah, I’m still seeing large amounts of traffic when jenny runs, so I guess it’s not yet fixed. But I didn’t mean to shame you. 😁 At least on my end, it’s not really an issue. 👌
@prologic Yeah, I’m still seeing large amounts of traffic when jenny runs, so I guess it’s not yet fixed. But I didn’t mean to shame you. 😁 At least on my end, it’s not really an issue. 👌
@prologic Yeah, I’m still seeing large amounts of traffic when jenny runs, so I guess it’s not yet fixed. But I didn’t mean to shame you. 😁 At least on my end, it’s not really an issue. 👌