# 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 28
# self = https://watcher.sour.is/conv/g5p2pva
π£ NEW: I realize we're still in a "code freeze" for Yarn.social's backend yarnd; however I wanted to share a new feature that just got built this weekend.
WebSub
This means the following two experimental features are not complementary and can hopefully both be promoted soonβ’ π€
- moving_average_feed_refresh
- websub
I would encourage anyone that normally runs yarnd from the main branch or the prologic/yarnd:latest Docker Image to give this a try and report any issues you come across!
You can enable this feature websub or both websub and moving_average_feed_refresh
in your Manage Pod UI and entering the features there one per line and
hitting "Save".
Thank you! πββοΈ
π£ NEW: I realize we're still in a "code freeze" for Yarn.social's backend yarnd; however I wanted to share a new feature that just got built this weekend.
WebSub
This means the following two experimental features are not complementary and can hopefully both be promoted soonβ’ π€
- moving_average_feed_refresh
- websub
I would encourage anyone that normally runs yarnd from the main branch or the prologic/yarnd:latest Docker Image to give this a try and report any issues you come across!
You can enable this feature websub or both websub and moving_average_feed_refresh
in your Manage Pod UI and entering the features there one per line and
hitting "Save".
Thank you! πββοΈ
@prologic, what are the visible subtleties for users? To see timeline, discovery, and mention changes now one must manually reload pages. Are these features changing this? How does this affects --fetch-interval ?
@david My apologies @david πββοΈ I _should_ have done a better job here in documenting the new feature (maybe that's why it's still feature gated? π€£) -- Nevertheless...
> what are the visible subtleties for users?
Hopefully none. The _only noticeable difference for cross-pod users in the Yarn.social network is real-time(ish) feed/cache refreshes as User A on Pod X makes a Twt and User B on Pod Y sees it within ~5s or so.~_
@david My apologies @david πββοΈ I _should_ have done a better job here in documenting the new feature (maybe that's why it's still feature gated? π€£) -- Nevertheless...
> what are the visible subtleties for users?
Hopefully none. The _only noticeable difference for cross-pod users in the Yarn.social network is real-time(ish) feed/cache refreshes as User A on Pod X makes a Twt and User B on Pod Y sees it within ~5s or so._~
> To see timeline, discovery, and mention changes now one must manually reload pages. Are these features changing this?
No, this will likely never change with the SSR (Server-Side Rendered) yarnd Web Interface as-is. We _may_ (I've been talking about it for a while now) introduce a "You have X new items, Click here to refresh" banner at the top at some point when @ullarah and I figure out how to build that.
> To see timeline, discovery, and mention changes now one must manually reload pages. Are these features changing this?
No, this will likely never change with the SSR (Server-Side Rendered) yarnd Web Interface as-is. We _may_ (I've been talking about it for a while now) introduce a "You have X new items, Click here to refresh" banner at the top at some point when @ullarah and I figure out how to build that.
> How does this affects --fetch-interval
Basically, fetching "subscribed" feeds will be done via WebSub. During the Cache fetch cycle, which is controlled by --fetch-interval, subscribed feeds are skipped.
This has the effect of reducing inbound and outbound load on pods via "polling" and instead pods are notified in _near_ real-time of a feed on a Pod being updated (note this is a yarnd only feature).
> How does this affects --fetch-interval
Basically, fetching "subscribed" feeds will be done via WebSub. During the Cache fetch cycle, which is controlled by --fetch-interval, subscribed feeds are skipped.
This has the effect of reducing inbound and outbound load on pods via "polling" and instead pods are notified in _near_ real-time of a feed on a Pod being updated (note this is a yarnd only feature).
@prologic very nice! I noticed that replies show much faster indeed. This is a very good addition. Good work!
@david Wow! π³ High praise π₯³ Thanks @david πββοΈ
@david Wow! π³ High praise π₯³ Thanks @david πββοΈ
One thing I'd like to show and point out is the effect this feature has had on my Pod alone:
twtxt.net CPU Load
The dip back up was me turning it off to fix some bugs π
One thing I'd like to show and point out is the effect this feature has had on my Pod alone:
twtxt.net CPU Load
The dip back up was me turning it off to fix some bugs π
@prologic I love seeing Yarn.social improve. Great addition!
@prologic Interesting, I updated to latest and can't enable Websub π€
Error extracting features: Error unrecognised feature: websub (available features: foo moving_average_feed_refresh jump_timeline_age)
Still on 0.12.0@f23c61b apparently π€
@screem How did you "update"? There is no new binary release yet... You either have to "build from source" or run the latest Docker image prologic/yarnd:latest -- If you do the later, you _might_ have to docker pull prologic/yarnd first π
@screem How did you "update"? There is no new binary release yet... You either have to "build from source" or run the latest Docker image prologic/yarnd:latest -- If you do the later, you _might_ have to docker pull prologic/yarnd first π
@prologic Ah, I'll need to pull the image then π
@screem Well done π₯³ I _assume_ you've now enabled websub too π
@screem Well done π₯³ I _assume_ you've now enabled websub too π
@news I will try later today maybe tomorrow and provide some feedback if I find out, what these tings do.
It's really nice to see the CPU usage reduced by quite a lot (especially on my pod, which is quite a bit busier)
Has anyone else noticed drops in CPU usage on their Pods since enabling websub? π€
It's really nice to see the CPU usage reduced by quite a lot (especially on my pod, which is quite a bit busier)
Has anyone else noticed drops in CPU usage on their Pods since enabling websub? π€
