# 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 61083
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38691
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38791
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38591
@marado Yup completely agree 💯 My goals with Yarn.social was basically always just to provide the tools and convenience for everyday folks 😆 But it's still Twtxt if that makes sense? 🤞
@marado Yup completely agree 💯 My goals with Yarn.social was basically always just to provide the tools and convenience for everyday folks 😆 But it's still Twtxt if that makes sense? 🤞
@marado I really like what you said [here}(https://twitter.com/mind_booster/status/1592483680211329025) although I don't think my translation does it justice, so maybe you can re-iterate it here in English? 🤔 IIUC I _think_ you're saying Yarn.social / Twtxt is quite a bit different as we place more of an emphasis on the "decentralisation" rather than "building a network and protocols", if so, this is true, as I _try_ to refer to things as "ecosystem" and "specs".
@marado I really like what you said [here}(https://twitter.com/mind_booster/status/1592483680211329025) although I don't think my translation does it justice, so maybe you can re-iterate it here in English? 🤔 IIUC I _think_ you're saying Yarn.social / Twtxt is quite a bit different as we place more of an emphasis on the "decentralisation" rather than "building a network and protocols", if so, this is true, as I _try_ to refer to things as "ecosystem" and "specs".
@marado I really like what you said [here}(https://twitter.com/mind_booster/status/1592483680211329025) although I don't think my translation does it justice, so maybe you can re-iterate it here in English? 🤔 IIUC I _think_ you're saying Yarn.social / Twtxt is quite a bit different as we place more of an emphasis on the "decentralisation" rather than "building a network and protocols", if so, this is true, as I _try_ to refer to things as "ecosystem" and "specs".
@marado I really like what you said [here}(https://twitter.com/mind_booster/status/1592483680211329025) although I don't think my translation does it justice, so maybe you can re-iterate it here in English? 🤔 IIUC I _think_ you're saying Yarn.social / Twtxt is quite a bit different as we place more of an emphasis on the "decentralisation" rather than "building a network and protocols", if so, this is true, as I _try_ to refer to things as "ecosystem" and "specs".
@stigatle Can you hit any of my other sites? 🤔
@stigatle Can you hit any of my other sites? 🤔
@stigatle Can you hit any of my other sites? 🤔
@stigatle Can you hit any of my other sites? 🤔
@stigatle If it's that old, usually just grabbing a newer ca-certificates bundle is usually enough? 🤔
@stigatle If it's that old, usually just grabbing a newer ca-certificates bundle is usually enough? 🤔
@stigatle If it's that old, usually just grabbing a newer ca-certificates bundle is usually enough? 🤔
@stigatle If it's that old, usually just grabbing a newer ca-certificates bundle is usually enough? 🤔
@abucci Yeah I agree. We really have to have the "right" controls in place, and so far I _think_ we do 🤔
@abucci Yeah I agree. We really have to have the "right" controls in place, and so far I _think_ we do 🤔
@abucci Yeah I agree. We really have to have the "right" controls in place, and so far I _think_ we do 🤔
@abucci Yeah I agree. We really have to have the "right" controls in place, and so far I _think_ we do 🤔
@abucci
> technology does not solve human social problems for you
This is sadly true 😅
@abucci
> technology does not solve human social problems for you
This is sadly true 😅
@abucci
> technology does not solve human social problems for you
This is sadly true 😅
@abucci
> technology does not solve human social problems for you
This is sadly true 😅
@stigatle Oh dear god 😅 There doesn't seem to be an issue here, I use Let's Encrypt wildcard certs, I wonder if you're missing the CA somehow? 🤔
@stigatle Oh dear god 😅 There doesn't seem to be an issue here, I use Let's Encrypt wildcard certs, I wonder if you're missing the CA somehow? 🤔
@stigatle Oh dear god 😅 There doesn't seem to be an issue here, I use Let's Encrypt wildcard certs, I wonder if you're missing the CA somehow? 🤔
@stigatle Oh dear god 😅 There doesn't seem to be an issue here, I use Let's Encrypt wildcard certs, I wonder if you're missing the CA somehow? 🤔
So @lyse I _think_ Have to also improve yarnd's feed rotation to do something like preserve up to --max-cache-size twts in the main feed, otherwise the cache gets a bit "empty" with unexpected behaviour 😢
So @lyse I _think_ Have to also improve yarnd's feed rotation to do something like preserve up to --max-cache-size twts in the main feed, otherwise the cache gets a bit "empty" with unexpected behaviour 😢
So @lyse I _think_ Have to also improve yarnd's feed rotation to do something like preserve up to --max-cache-size twts in the main feed, otherwise the cache gets a bit "empty" with unexpected behaviour 😢
So @lyse I _think_ Have to also improve yarnd's feed rotation to do something like preserve up to --max-cache-size twts in the main feed, otherwise the cache gets a bit "empty" with unexpected behaviour 😢
The _problem_ is Mastodon is _really_ a "distributed" network, not _really_ "decentralised" per se, it is and is isn't in the strictest sense. Instances get far too large, and you can see what happens when they grow even larger, they strain and struggle to keep up with the load and traffic on them.
Blocking bad instances is necessary, but it wouldn't be as necessary if instances were much smaller IMO.
The _problem_ is Mastodon is _really_ a "distributed" network, not _really_ "decentralised" per se, it is and is isn't in the strictest sense. Instances get far too large, and you can see what happens when they grow even larger, they strain and struggle to keep up with the load and traffic on them.
Blocking bad instances is necessary, but it wouldn't be as necessary if instances were much smaller IMO.
The _problem_ is Mastodon is _really_ a "distributed" network, not _really_ "decentralised" per se, it is and is isn't in the strictest sense. Instances get far too large, and you can see what happens when they grow even larger, they strain and struggle to keep up with the load and traffic on them.
Blocking bad instances is necessary, but it wouldn't be as necessary if instances were much smaller IMO.
The _problem_ is Mastodon is _really_ a "distributed" network, not _really_ "decentralised" per se, it is and is isn't in the strictest sense. Instances get far too large, and you can see what happens when they grow even larger, they strain and struggle to keep up with the load and traffic on them.
Blocking bad instances is necessary, but it wouldn't be as necessary if instances were much smaller IMO.
@darch It's a good visualisation and great explanation 👌
@darch It's a good visualisation and great explanation 👌
@darch It's a good visualisation and great explanation 👌
@darch It's a good visualisation and great explanation 👌
Hmm I _think_ my feed hit the --max-fetch-limit size and I don't think yarnd deals with this dynamically when its reached, only in a daily background job 🤦♂️
Hmm I _think_ my feed hit the --max-fetch-limit size and I don't think yarnd deals with this dynamically when its reached, only in a daily background job 🤦♂️
Hmm I _think_ my feed hit the --max-fetch-limit size and I don't think yarnd deals with this dynamically when its reached, only in a daily background job 🤦♂️
Hmm I _think_ my feed hit the --max-fetch-limit size and I don't think yarnd deals with this dynamically when its reached, only in a daily background job 🤦♂️
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Hmm looks like you found a bug with indexing conversations that spanned across the time when we switch from #<xxxx url> to just #xxxx 🤔 I'll have to debug this...
@lyse Yeah as we discussed in the call, I _think_ I might switch this to use a UNIX timestamp instead with seconds precision. Because the feeds' metadata are dynamically generated I have to do handle feed rotation and linking with the prev field more programatically I guess 😅
@lyse Yeah as we discussed in the call, I _think_ I might switch this to use a UNIX timestamp instead with seconds precision. Because the feeds' metadata are dynamically generated I have to do handle feed rotation and linking with the prev field more programatically I guess 😅
@lyse Yeah as we discussed in the call, I _think_ I might switch this to use a UNIX timestamp instead with seconds precision. Because the feeds' metadata are dynamically generated I have to do handle feed rotation and linking with the prev field more programatically I guess 😅
@lyse Yeah as we discussed in the call, I _think_ I might switch this to use a UNIX timestamp instead with seconds precision. Because the feeds' metadata are dynamically generated I have to do handle feed rotation and linking with the prev field more programatically I guess 😅
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@lyse Hah you never shared this nice story before 😅 Very nice! 👌
@eldersnake Probably quite unlikely I'd say. I maintain backwards periods for long periods of time.
@eldersnake Probably quite unlikely I'd say. I maintain backwards periods for long periods of time.
@eldersnake Probably quite unlikely I'd say. I maintain backwards periods for long periods of time.
@eldersnake Probably quite unlikely I'd say. I maintain backwards periods for long periods of time.
@eldersnake OH man 😅 Glad you're okay, alive and kick'n ! 🤗 Sorry to hear you're going through a rough patch 😢
@eldersnake OH man 😅 Glad you're okay, alive and kick'n ! 🤗 Sorry to hear you're going through a rough patch 😢
@eldersnake OH man 😅 Glad you're okay, alive and kick'n ! 🤗 Sorry to hear you're going through a rough patch 😢
@eldersnake OH man 😅 Glad you're okay, alive and kick'n ! 🤗 Sorry to hear you're going through a rough patch 😢
@darch I'm so confused 😅 See you in a few hours 🤗 Anyone else coming to at 1100 UTC? 🤔
@darch I'm so confused 😅 See you in a few hours 🤗 Anyone else coming to at 1100 UTC? 🤔
@darch I'm so confused 😅 See you in a few hours 🤗 Anyone else coming to at 1100 UTC? 🤔
@darch I'm so confused 😅 See you in a few hours 🤗 Anyone else coming to at 1100 UTC? 🤔
@justamoment Nice! 👌 The _only_ thing I think you/I need to figure out is what kind of endpoint you need to hit and what kind of data you want back in order to know whether to popup a banner and how many new twts are in your timeline since you last refreshed I guess? 🤔
@justamoment Nice! 👌 The _only_ thing I think you/I need to figure out is what kind of endpoint you need to hit and what kind of data you want back in order to know whether to popup a banner and how many new twts are in your timeline since you last refreshed I guess? 🤔
@justamoment Nice! 👌 The _only_ thing I think you/I need to figure out is what kind of endpoint you need to hit and what kind of data you want back in order to know whether to popup a banner and how many new twts are in your timeline since you last refreshed I guess? 🤔
@justamoment Nice! 👌 The _only_ thing I think you/I need to figure out is what kind of endpoint you need to hit and what kind of data you want back in order to know whether to popup a banner and how many new twts are in your timeline since you last refreshed I guess? 🤔
@darch But you're awake now? Next time-slot is at 1100 UTC 😅
@darch But you're awake now? Next time-slot is at 1100 UTC 😅
@darch But you're awake now? Next time-slot is at 1100 UTC 😅
@darch But you're awake now? Next time-slot is at 1100 UTC 😅
