# 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 17
# self = https://watcher.sour.is/conv/y4xbttq
@fastidious You obviously changed base urls in-between? 🤔 I'll write some code to automagically amend/fix this, otherwise just nuke your database (_not the data dir_) and let it rebuild the database (_you'll have to re-create your accounts though_)
@fastidious You obviously changed base urls in-between? 🤔 I'll write some code to automagically amend/fix this, otherwise just nuke your database (_not the data dir_) and let it rebuild the database (_you'll have to re-create your accounts though_)
> Conversations across pods are iffy
Also define "iffy"? If you're observing the same problem of decentralised systems where you may or may not be able to view a conversation because your pod hasn't seen it, this is a _known problem_ and is being addressed by integrating pods with the Yarns search engine. That is to say a global search engine will help fill in missing gaps.
> Conversations across pods are iffy\n\nAlso define "iffy"? If you're observing the same problem of decentralised systems where you may or may not be able to view a conversation because your pod hasn't seen it, this is a _known problem_ and is being addressed by integrating pods with the Yarns search engine. That is to say a global search engine will help fill in missing gaps.
> Conversations across pods are iffy
Also define "iffy"? If you're observing the same problem of decentralised systems where you may or may not be able to view a conversation because your pod hasn't seen it, this is a _known problem_ and is being addressed by integrating pods with the Yarns search engine. That is to say a global search engine will help fill in missing gaps.
@fastidious No it won't. The search engine is also designed to be self-hosted. Pods will have a default configuration that points to https://search.twtxt.net but you could run your own for example.
@fastidious No it won't. The search engine is also designed to be self-hosted. Pods will have a default configuration that points to https://search.twtxt.net but you could run your own for example.
Only other way to do it is p2p between pods, but that isn't completely backwards compatible and introduces a new protocol between pods, right now pods really use the same HTTP + Twtxt as their "underlying protocol", the search engine is supplementary and works across the entire Yarn.social / Twtxt space...
Only other way to do it is p2p between pods, but that isn't completely backwards compatible and introduces a new protocol between pods, right now pods really use the same HTTP + Twtxt as their "underlying protocol", the search engine is supplementary and works across the entire Yarn.social / Twtxt space...
For example if I weren't following @lyse (_I obviously am!_); Then if say @jlj (_he runs a pod too_) and I were having a conversation and @lyse chimed neither pod would see this because @lyse basically hosts his feed using his own server, and uses his own client and adheres to the various Twt Extensions created on and around the original spec.
For example if I weren't following @lyse (_I obviously am!_); Then if say @jlj (_he runs a pod too_) and I were having a conversation and @lyse chimed neither pod would see this because @lyse basically hosts his feed using his own server, and uses his own client and adheres to the various Twt Extensions created on and around the original spec.
@prologic On the plus side with the way that works, if on the off-chance you want to essentially put someone on ignore, you just unfollow them. No ignore list needed, and it's like they don't exist.
@eldersnake Actually... You can "Mute" and "Unmute" feeds from the Web Interface and API (_mobile app; Goryon_) too 👌
@eldersnake Actually... You can "Mute" and "Unmute" feeds from the Web Interface and API (_mobile app; Goryon_) too 👌
@prologic Huh, I didn't know that. Not that I need to use it, but where is the Mute on the web interface? 🤔 (knowing my luck, it's right in front of me and I'm somehow missing it)
@eldersnake D’oh 🤦♂️ I didn’t add the UI for external feeds. Let me fix that today real quick 🤣
@eldersnake D’oh 🤦♂️ I didn’t add the UI for external feeds. Let me fix that today real quick 🤣