# 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 23
# self = https://watcher.sour.is/conv/4kw64qq
@prologic cool, so can this be used to improve the data quality of various nicks on each pod? I don't see a "nick": field in the JSON
@darch In any case I don' think adding nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
@darch In any case I don' think adding nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
@darch In any case I don' think adding nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
@darch In any case I don' think adding nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
@prologic so anyway people should start using the longform mentions of @nick@url and not just @nick and the the client (yarnd) need to verify it and convert it to the proper mentions. Maybe even just as @source.url>@ to omitting the spreading of bad nicks. (Ref: [twtxt file — twtxt 1.3.2-dev documentation](https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html) )
@prologic so anyway people should start using the longform mentions of @nick@url and not just @nick and the the client (yarnd) need to verify it and convert it to the proper mentions. Maybe even just as @<source.url> over @<source.nick> to omitting the spreading of bad nicks. (Ref: twtxt file — twtxt 1.3.2-dev documentation )
@prologic so anyway people should start using the longform mentions of @nick@url and not just @nick and the the client (yarnd) need to verify it and convert it to the proper mentions. Maybe even just as <@source.url> over @<source.nick source.url> to omitting the spreading of bad nicks. (Ref: twtxt file — twtxt 1.3.2-dev documentation )
@prologic so anyway people should start using the longform mentions of @nick@url and not just @nick and the the client (yarnd) need to verify it and convert it to the proper mentions. Maybe even just as @<source.url> instead of @<source.nick source.url> to omitting the spreading of bad nicks. (Ref: twtxt file — twtxt 1.3.2-dev documentation
@darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? -mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅
@darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? -mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅
@darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? -mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅
@darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? -mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅
@prologic My point was also that the client should match and replace @prologic with @<https://twtxt.net/user/prologic/twtxt.txt> and prompt the use in some way if there are more than one prologic like yarnd already does with the popup and autofill.
@darch Ahh you mean rewrite -mentions into their fully formed Twtxt mention special URLs? 🤔
@darch Ahh you mean rewrite -mentions into their fully formed Twtxt mention special URLs? 🤔
@darch Ahh you mean rewrite -mentions into their fully formed Twtxt mention special URLs? 🤔
@darch Ahh you mean rewrite -mentions into their fully formed Twtxt mention special URLs? 🤔
I mean yeah sure, yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
I mean yeah sure, yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
I mean yeah sure, yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
I mean yeah sure, yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
@prologic yes and leaving out the nicks which you can also not really edit when they are saved to to yarnd following list. You need to delete and re-add them. But if we get around to building something like this http://darch.dk/yarn/lists-mockup-01.html then it would be easier to fix