# 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 27
# self = https://watcher.sour.is/conv/ywqpb6a
Hi @t0rcke! π Welcome to my pod! ππ
@t0rcke @jlj Aelcome! π
This is something Iβm hoping to improve with the integration of yarns (the search engine)
π
@t0rcke @jlj Aelcome! π
This is something Iβm hoping to improve with the integration of yarns (the search engine)
π
@t0rcke @jlj Aelcome! π\n\nThis is something Iβm hoping to improve with the integration of yarns (the search engine)\n\n\n\nπ
@jlj Oh interesting! π€ You replied to (_rightfully so_) the @twtxt bot when it posted the FOLLOW event of a new user (_you always follow yourself!_) But as I don't follow that feed from your pod the "conversation" is broken for me (_at least on Goryon_) and missing from the Web UI on my pod. Hmmmm π€ I'm not even sure how the yarns search engine would help solve this? This is a bit of a difficult problem I've been thinking about for months now... This is hard, but not impossible π
@jlj Oh interesting! π€ You replied to (_rightfully so_) the @twtxt bot when it posted the FOLLOW event of a new user (_you always follow yourself!_) But as I don't follow that feed from your pod the "conversation" is broken for me (_at least on Goryon_) and missing from the Web UI on my pod. Hmmmm π€ I'm not even sure how the yarns search engine would help solve this? This is a bit of a difficult problem I've been thinking about for months now... This is hard, but not impossible π
But I donβt actually need to follow the fees per se, my pod just needs to fetch it occasionally π€
But I donβt actually need to follow the fees per se, my pod just needs to fetch it occasionally π€
But I donβt actually need to follow the fees per se, my pod just needs to fetch it occasionally π€\n\n
So maybe... The Yarns search engine _can_ fill in missing gaps. I'd better get working on an API for that soon and integration into yarnd with a configurable "default search engine" option.
So maybe... The Yarns search engine _can_ fill in missing gaps. I'd better get working on an API for that soon and integration into yarnd with a configurable "default search engine" option.
I do have to say though, that the overall "decentralized" / "federated" experience ia maybe ~90% there though... π -- Assuming @t0rcke become an active user on your pod π then he/she will discover me from that conversation already just by the fact you follow me π~
I do have to say though, that the overall "decentralized" / "federated" experience ia maybe ~90% there though... π -- Assuming @t0rcke become an active user on your pod π then he/she will discover me from that conversation already just by the fact you follow me π~
@t0rcke @prologic the potential is well and truly there. I love the idea of one day entire families being on a pod, especially the idea that someone self hosts and their whole household is on that pod, plus whoever else joins if they make it public registration. I dunno, sounds cool to me. Instead of congregating on Farcebook. One can dream...
@prologic @twtxt Yeah, I always have the same problem with your /. replies. π But, as @lohn says, it's just a matter an extra step to visit the whole conversation on your pod.
@jlj @lohn This is why I _think_ it's important that the Yarns search engine and _once implemented_ the one at https://search.twtxt.net _actually_ re-crawl active feeds more often with some sensible algorithm. I'm already tracking moving averages for "fetch time" and "new posts", so it'll be interesting to see those numbers soon, but if we agree this is a good idea I _think_ it _could_ help solve this very problem by the yarnd backend going:\n\n> Oh oops, I don't have that hash, lemme go see if my configured search engine does.\n> Yes? Fetch and cache.
@jlj @lohn This is why I _think_ it's important that the Yarns search engine and _once implemented_ the one at https://search.twtxt.net _actually_ re-crawl active feeds more often with some sensible algorithm. I'm already tracking moving averages for "fetch time" and "new posts", so it'll be interesting to see those numbers soon, but if we agree this is a good idea I _think_ it _could_ help solve this very problem by the yarnd backend going:
> Oh oops, I don't have that hash, lemme go see if my configured search engine does.
> Yes? Fetch and cache.
@jlj @lohn This is why I _think_ it's important that the Yarns search engine and _once implemented_ the one at https://search.twtxt.net _actually_ re-crawl active feeds more often with some sensible algorithm. I'm already tracking moving averages for "fetch time" and "new posts", so it'll be interesting to see those numbers soon, but if we agree this is a good idea I _think_ it _could_ help solve this very problem by the yarnd backend going:
> Oh oops, I don't have that hash, lemme go see if my configured search engine does.
> Yes? Fetch and cache.
@jlj @prologic I liked this idea. And the search feature will be distributed/federated too?