# 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 20
# self = https://watcher.sour.is/conv/y5rkw5a
📣 NEW: Announcing the new and improved Yarns search engine and crawler! search.twtxt.net -- [Example search for "Hello World"](https://search.twtxt.net/search?q=Hello World) Enjoy! 🤗 -- @darch When you have this, this is what we need to work on in terms of improving the UI/UX. As a first step you should probably try to apply the same SimpleCSS to this codebase and go from there. -- In the end (didn't happen yet, time/effort) most of the code here in yarns will get reused directly into yarnd, except that I'll use the bluge indexer instead.
📣 NEW: Announcing the new and improved Yarns search engine and crawler! search.twtxt.net -- [Example search for "Hello World"](https://search.twtxt.net/search?q=Hello World) Enjoy! 🤗 -- @darch When you have this, this is what we need to work on in terms of improving the UI/UX. As a first step you should probably try to apply the same SimpleCSS to this codebase and go from there. -- In the end (didn't happen yet, time/effort) most of the code here in yarns will get reused directly into yarnd, except that I'll use the bluge indexer instead.
@prologic great work. All booked this weekend with AFK stuff, but hope I will have time next week to do something about the UI/UX
@darch No problems no problems! 👌 Meanwhile lemme know if you have any feedback or find any bugs. I also updated the Help page so hopefully that helps new users 🤞
@darch No problems no problems! 👌 Meanwhile lemme know if you have any feedback or find any bugs. I also updated the Help page so hopefully that helps new users 🤞
@prologic Cool. I'd like to be able to easily visit the conversation of a found twt by following a link. The yarnd URL could be configurable in the settings, so people operating both yarnd and yarns could just link to their own instance.
@prologic, search for "quark" and you will get quack, quart, quirk, and all possible iterations. Not too helpful.
@quark try switching to query string under options 
@quark Are you sure? 🤔 
You've probably just been away so long that you haven't come up in any feeds until recently? I'm missing a few hundred thousand Twts from the index but working on re-ingesting older archives 🤞
@quark Are you sure? 🤔 You've probably just been away so long that you haven't come up in any feeds until recently? I'm missing a few hundred thousand Twts from the index but working on re-ingesting older archives 🤞
@quark Btw, if you _wanted_ to search for all mentions of you, you'd do a Term Query against the mentions field like this or a Query String search with a query like mentions:quark@ferengi.one
@quark Btw, if you _wanted_ to search for all mentions of you, you'd do a Term Query against the mentions field like this or a Query String search with a query like mentions:quark@ferengi.one
Down the line I like to see that the end user will be offer three leves if search:
- Personal(ized) for only searching in feeds you follow (scope: Timeline)
- Local/pod for search only feeds that are hosted or followed by other people on your home pod (scope: Discover)
- Global for searching in all indexed feed
Maybe the 2nd level can be skipped, but it might become usefulness if the network grows and we get pods with special profiles like regional ones
@darch Can I ask why we'd want to split our the index into 3 different parts? This would involve creating 3 separate indexes and creating quite a bit of complexity with the cache and feed investor.
@darch Can I ask why we'd want to split our the index into 3 different parts? This would involve creating 3 separate indexes and creating quite a bit of complexity with the cache and feed investor.
@prologic I do't want to split the index in 3. The first two would be on the user's home pod only, a then you would be taken to a yarns instance
for the global search