# 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 43
# self = https://watcher.sour.is/conv/ul5gdnq
@win0err glad to help! Trying to be a good netizen over here.
it does raise an interesting question of whether I should try to re-implement the exponential back off algorithm again?
it does raise an interesting question of whether I should try to re-implement the exponential back off algorithm again?
it does raise an interesting question of whether I should try to re-implement the exponential back off algorithm again?
it does raise an interesting question of whether I should try to re-implement the exponential back off algorithm again?
I tried once, but I couldn't get it to work just right
I tried once, but I couldn't get it to work just right
I tried once, but I couldn't get it to work just right
I tried once, but I couldn't get it to work just right
@prologic not to be a jerk, but exponential backoff is a one-liner in most of the scala stream processing libraries of note. π
@abucci Haha π€£ You jerk π (kidding) -- Would you have time to go over the implementation/algorithm I _once_ tried but was never happy with? π€ π Maybe we can bring it back and improve/fix it.
@abucci Haha π€£ You jerk π (kidding) -- Would you have time to go over the implementation/algorithm I _once_ tried but was never happy with? π€ π Maybe we can bring it back and improve/fix it.
@abucci Haha π€£ You jerk π (kidding) -- Would you have time to go over the implementation/algorithm I _once_ tried but was never happy with? π€ π Maybe we can bring it back and improve/fix it.
@abucci Haha π€£ You jerk π (kidding) -- Would you have time to go over the implementation/algorithm I _once_ tried but was never happy with? π€ π Maybe we can bring it back and improve/fix it.
@abucci Also sorry about the confusing shitβ’ last night (it was late for me) π€¦ββοΈ I should have jut said:
1. Go to Setting
2. Poderater Setting
3. Reset Cache
π
@abucci Also sorry about the confusing shitβ’ last night (it was late for me) π€¦ββοΈ I should have jut said:
1. Go to Setting
2. Poderater Setting
3. Reset Cache
π
@abucci Also sorry about the confusing shitβ’ last night (it was late for me) π€¦ββοΈ I should have jut said:
1. Go to Setting
2. Poderater Setting
3. Reset Cache
π
@abucci Also sorry about the confusing shitβ’ last night (it was late for me) π€¦ββοΈ I should have jut said:
1. Go to Setting
2. Poderater Setting
3. Reset Cache
π
@prologic sure just point me at the right spot in the code. I actually have sone free time tomorrow so it's good timing!
@prologic no worries! It got sorted, which is what matters.
For some context, I was trying to work out a way to calculate the moving average of a feed and how often it updates and converge on this. So feeds that update frequently are always fetched at the fetch interval configured by the pod operator (default 5m) and feeds that update slowly are fetched less frequently.
For some context, I was trying to work out a way to calculate the moving average of a feed and how often it updates and converge on this. So feeds that update frequently are always fetched at the fetch interval configured by the pod operator (default 5m) and feeds that update slowly are fetched less frequently.
For some context, I was trying to work out a way to calculate the moving average of a feed and how often it updates and converge on this. So feeds that update frequently are always fetched at the fetch interval configured by the pod operator (default 5m) and feeds that update slowly are fetched less frequently.
For some context, I was trying to work out a way to calculate the moving average of a feed and how often it updates and converge on this. So feeds that update frequently are always fetched at the fetch interval configured by the pod operator (default 5m) and feeds that update slowly are fetched less frequently.
For cross-pod fetches, this has no effect as pods now should be using WebSub by default (depending on the version) and at some point I _might_ also add WebSub support to the feeds.twtxt.net service π
For cross-pod fetches, this has no effect as pods now should be using WebSub by default (depending on the version) and at some point I _might_ also add WebSub support to the feeds.twtxt.net service π
For cross-pod fetches, this has no effect as pods now should be using WebSub by default (depending on the version) and at some point I _might_ also add WebSub support to the feeds.twtxt.net service π
For cross-pod fetches, this has no effect as pods now should be using WebSub by default (depending on the version) and at some point I _might_ also add WebSub support to the feeds.twtxt.net service π
@prologic This seems to have worked--@win0err emailed me saying that my pod is no longer fetching their feed every five minutes. Thanks for your help!