# 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 61078
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42791
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42891
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42691
@marado i'm actually very pissed off at Apple, about looking for new revenue sources by turning to the tater, but they happen to have on their users. I have historically trusted Apple, because it's never been in the business of advertising. Apple already makes enough fucking money. π€¦ββοΈ
@marado i'm actually very pissed off at Apple, about looking for new revenue sources by turning to the tater, but they happen to have on their users. I have historically trusted Apple, because it's never been in the business of advertising. Apple already makes enough fucking money. π€¦ββοΈ
@marado i'm actually very pissed off at Apple, about looking for new revenue sources by turning to the tater, but they happen to have on their users. I have historically trusted Apple, because it's never been in the business of advertising. Apple already makes enough fucking money. π€¦ββοΈ
ZFS Operations: Replacing a failed disk - HedgeDoc -- Had to replace a failed disk in my NAS today as it was on its way out. For anyone else running a ZFS pool, here's the steps involved:
1. zpool offline <pool> <device>
2. Remove failed disk and replace with new disk.
3. zpool replace <pool> <device>
4. Wait.
#ZFS
ZFS Operations: Replacing a failed disk - HedgeDoc -- Had to replace a failed disk in my NAS today as it was on its way out. For anyone else running a ZFS pool, here's the steps involved:
1. zpool offline <pool> <device>
2. Remove failed disk and replace with new disk.
3. zpool replace <pool> <device>
4. Wait.
#ZFS
ZFS Operations: Replacing a failed disk - HedgeDoc -- Had to replace a failed disk in my NAS today as it was on its way out. For anyone else running a ZFS pool, here's the steps involved:
1. zpool offline <pool> <device>
2. Remove failed disk and replace with new disk.
3. zpool replace <pool> <device>
4. Wait.
#ZFS
ZFS Operations: Replacing a failed disk - HedgeDoc -- Had to replace a failed disk in my NAS today as it was on its way out. For anyone else running a ZFS pool, here's the steps involved:
1. ce>
2. Remove failed disk and replace with new disk.
3. zpool replace
4. Wait.
#ZFS
ZFS Operations: Replacing a failed disk - HedgeDoc -- Had to replace a failed disk in my NAS today as it was on its way out. For anyone else running a ZFS pool, here's the steps involved:
1. zpool offline <pool> <device>
2. Remove failed disk and replace with new disk.
3. zpool replace <pool> <device>
4. Wait.
#ZFS
@darch Yeah, so I'm not entirely convince it would really buy us much value... π€ I'll sleep on it π
@darch Yeah, so I'm not entirely convince it would really buy us much value... π€ I'll sleep on it π
@darch Yeah, so I'm not entirely convince it would really buy us much value... π€ I'll sleep on it π
@darch Yeah, so I'm not entirely convince it would really buy us much value... π€ I'll sleep on it π
@darch Hmmm I'm not sure it would really have that effect to be honest π€ -- And by "indirection" I meant that, you would make a Twt replying to an automated feed (whose source is from somewhere else), a webmention would be sent to that feed service, the feed service would receive the webmention, figure out the source of the feed and forward the webmention to the original source.
Hmmm π€
@darch Hmmm I'm not sure it would really have that effect to be honest π€ -- And by "indirection" I meant that, you would make a Twt replying to an automated feed (whose source is from somewhere else), a webmention would be sent to that feed service, the feed service would receive the webmention, figure out the source of the feed and forward the webmention to the original source.
Hmmm π€
@darch Hmmm I'm not sure it would really have that effect to be honest π€ -- And by "indirection" I meant that, you would make a Twt replying to an automated feed (whose source is from somewhere else), a webmention would be sent to that feed service, the feed service would receive the webmention, figure out the source of the feed and forward the webmention to the original source.
Hmmm π€
@darch Hmmm I'm not sure it would really have that effect to be honest π€ -- And by "indirection" I meant that, you would make a Twt replying to an automated feed (whose source is from somewhere else), a webmention would be sent to that feed service, the feed service would receive the webmention, figure out the source of the feed and forward the webmention to the original source.
Hmmm π€
Bloody hell π€¦ββοΈ 4 ~5m outages in 1 hour π€¬~
Bloody hell π€¦ββοΈ 4 ~5m outages in 1 hour π€¬~
Bloody hell π€¦ββοΈ 4 ~5m outages in 1 hour π€¬~
Bloody hell π€¦ββοΈ 4 ~5m outages in 1 hour π€¬~
@darch Hmmmtjats some indirection there π€ Can I ask why? π
@darch Hmmmtjats some indirection there π€ Can I ask why? π
@darch Hmmmtjats some indirection there π€ Can I ask why? π
@darch Hmmmtjats some indirection there π€ Can I ask why? π
@eaplmx No one minds π
The conversations are still good π
@eaplmx No one minds π
The conversations are still good π
@eaplmx No one minds π
The conversations are still good π
@eaplmx No one minds π
The conversations are still good π
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 π
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.
@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
π
@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 "hope" is a powerful human emotion indeed (or so I believe) and I think it's a great part of what makes us human π We should never let go of hope, no matter what the powerful assholes at the top try to throw at us π
@abucci "hope" is a powerful human emotion indeed (or so I believe) and I think it's a great part of what makes us human π We should never let go of hope, no matter what the powerful assholes at the top try to throw at us π
@abucci "hope" is a powerful human emotion indeed (or so I believe) and I think it's a great part of what makes us human π We should never let go of hope, no matter what the powerful assholes at the top try to throw at us π
@abucci "hope" is a powerful human emotion indeed (or so I believe) and I think it's a great part of what makes us human π We should never let go of hope, no matter what the powerful assholes at the top try to throw at us π
@abucci We're pretty much the same too, besides Google Apps (grandfathered account) and a few media/delivery services, I can't say we really rely on Cloudβ’ all that much (if at all) π
@abucci We're pretty much the same too, besides Google Apps (grandfathered account) and a few media/delivery services, I can't say we really rely on Cloudβ’ all that much (if at all) π
@abucci We're pretty much the same too, besides Google Apps (grandfathered account) and a few media/delivery services, I can't say we really rely on Cloudβ’ all that much (if at all) π
@abucci We're pretty much the same too, besides Google Apps (grandfathered account) and a few media/delivery services, I can't say we really rely on Cloudβ’ all that much (if at all) π
@abucci having read a couple of the tweets, I completely agree π― this guy ough to be shot and jailed for life π€¦ββοΈπ± Disgusting π’
@abucci having read a couple of the tweets, I completely agree π― this guy ough to be shot and jailed for life π€¦ββοΈπ± Disgusting π’
@abucci having read a couple of the tweets, I completely agree π― this guy ough to be shot and jailed for life π€¦ββοΈπ± Disgusting π’
@abucci having read a couple of the tweets, I completely agree π― this guy ough to be shot and jailed for life π€¦ββοΈπ± Disgusting π’
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
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?
@abucci I guess the frustrating thing about all this is that we don't stop and think of the consequences or implications π€¦ββοΈ I'm also mad about https://twtxt.net/twt/q2lc7sq π€¬
@abucci I guess the frustrating thing about all this is that we don't stop and think of the consequences or implications π€¦ββοΈ I'm also mad about https://twtxt.net/twt/q2lc7sq π€¬
@abucci I guess the frustrating thing about all this is that we don't stop and think of the consequences or implications π€¦ββοΈ I'm also mad about https://twtxt.net/twt/q2lc7sq π€¬
@abucci I guess the frustrating thing about all this is that we don't stop and think of the consequences or implications π€¦ββοΈ I'm also mad about https://twtxt.net/twt/q2lc7sq π€¬
@darch I meant about the original client, not an alternative frontend π
@darch I meant about the original client, not an alternative frontend π
@darch I meant about the original client, not an alternative frontend π
@darch I meant about the original client, not an alternative frontend π
@abucci I don't with a few minor exceptions I haven't gotten rid of (yet)
@abucci I don't with a few minor exceptions I haven't gotten rid of (yet)
@abucci I don't with a few minor exceptions I haven't gotten rid of (yet)
@abucci I don't with a few minor exceptions I haven't gotten rid of (yet)
@abucci Yes. That _should_ π€ do it. No restarting a pod won't delete the cache.
@abucci Yes. That _should_ π€ do it. No restarting a pod won't delete the cache.
@abucci Yes. That _should_ π€ do it. No restarting a pod won't delete the cache.
@abucci Yes. That _should_ π€ do it. No restarting a pod won't delete the cache.
Btw... The _only_ reason I can think of this not working as expected, is if the feed in fact hasn't changed at all and so therefore the cached Metadata is unchanged and therefore it believes there is no refresh interval. In order to bust the cache here, the user/feed has to post a Twt or you can Refresh your Pod's Cache.
Btw... The _only_ reason I can think of this not working as expected, is if the feed in fact hasn't changed at all and so therefore the cached Metadata is unchanged and therefore it believes there is no refresh interval. In order to bust the cache here, the user/feed has to post a Twt or you can Refresh your Pod's Cache.
Btw... The _only_ reason I can think of this not working as expected, is if the feed in fact hasn't changed at all and so therefore the cached Metadata is unchanged and therefore it believes there is no refresh interval. In order to bust the cache here, the user/feed has to post a Twt or you can Refresh your Pod's Cache.
Btw... The _only_ reason I can think of this not working as expected, is if the feed in fact hasn't changed at all and so therefore the cached Metadata is unchanged and therefore it believes there is no refresh interval. In order to bust the cache here, the user/feed has to post a Twt or you can Refresh your Pod's Cache.