# 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/6ietmfa
And it gets the hashtags and mentions just like the web version! Kudos @prologic! My only concern is the app name conflict. Yarn is a very know package manager for node.js.
@lohn This is true but we thought long and hard about how and what to rebrand the project to.

See here for the long discussion and the choice and why πŸ€—

those of us that are web developers are familiar with the package manager for Node.JS yes; but Yarn otherwise means to have a conversation ☺️
@lohn This is true but we thought long and hard about how and what to rebrand the project to.

See here for the long discussion and the choice and why πŸ€—

those of us that are web developers are familiar with the package manager for Node.JS yes; but Yarn otherwise means to have a conversation ☺️
@lohn This is true but we thought long and hard about how and what to rebrand the project to.\n\nSee here for the long discussion and the choice and why πŸ€—\n\nthose of us that are web developers are familiar with the package manager for Node.JS yes; but Yarn otherwise means to have a conversation ☺️
@prologic It was a nice thread. Didn't imagine that so many people was participating. But anyway, I wasn't talking about a name change. Just a filename change.
@prologic I already have nodejs's yarn installed (as many developers have) and I had to rename yarn social client executable to yarn-cli to avoid the conflict. I don't think that too many people would use CLI those days, but have to rename it is clearly a friction to adoption.
@lohn Oh yeah the binaries _could_ be renamed, especially the yarn command-line client. It still needs some more work, but it's otherwise already useful on the command-line.
@lohn Oh yeah the binaries _could_ be renamed, especially the yarn command-line client. It still needs some more work, but it's otherwise already useful on the command-line.
@lohn I'm open to suggestions. yarnd is okay for the daemon/server though? I agree with you in anycase; even if I'm one of those devs that actually don't really use yarn or npm myself (_even when I do web development_) -- I'm strange 🀣 cc @markwylde will attest to this πŸ˜‚
@lohn I'm open to suggestions. yarnd is okay for the daemon/server though? I agree with you in anycase; even if I'm one of those devs that actually don't really use yarn or npm myself (_even when I do web development_) -- I'm strange 🀣 cc @markwylde will attest to this πŸ˜‚
There's also other things in active use or in development, e.g: rss2twtxt which powers feeds.twtxt.net and there is a search engine for the Twtxt ecosystem/space itself (_which yarnd is basically a fancy client and server hosting platform of_). So binary names are and name ideas for various components are more than welcome! πŸ™‡β€β™‚οΈ
There's also other things in active use or in development, e.g: rss2twtxt which powers feeds.twtxt.net and there is a search engine for the Twtxt ecosystem/space itself (_which yarnd is basically a fancy client and server hosting platform of_). So binary names are and name ideas for various components are more than welcome! πŸ™‡β€β™‚οΈ
@prologic @markwylde everyone has its idiosyncrasies. I'm using win 11, for example. But I can say that npm/yarn are not missing because everything here is great.
@prologic @markwylde and yarnd is a great name for the server binary. I was thinking of something like yarnc (this is what I'm using here) 😁
@prologic I see that you crosspost between micro.blog and twtxt. Are you using rss2twtxt for it?
@lohn Nope, rss2twtxt goes in the direction of "thing" -> "twtxt". It supports RSS, Atom and now Twitter.

To cross-post to my micro.Blob account I just added my RSS/Atom Feed which you can find on your profile page. Basically Yarn.social pods are very interoperable with both RSS/Atom and Twtxt.
@lohn Nope, rss2twtxt goes in the direction of "thing" -> "twtxt". It supports RSS, Atom and now Twitter.\n\nTo cross-post to my micro.Blob account I just added my RSS/Atom Feed which you can find on your profile page. Basically Yarn.social pods are very interoperable with both RSS/Atom and Twtxt.
@lohn Nope, rss2twtxt goes in the direction of "thing" -> "twtxt". It supports RSS, Atom and now Twitter.

To cross-post to my micro.Blob account I just added my RSS/Atom Feed which you can find on your profile page. Basically Yarn.social pods are very interoperable with both RSS/Atom and Twtxt.
Also I like the yarnc binary name for the cli client. I might just do that πŸ‘Œ
Also I like the yarnc binary name for the cli client. I might just do that πŸ‘Œ