# 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 12
# self = https://watcher.sour.is/conv/w46jk3q
@duriny_test LOL! 😂 Pretty hard to ignore when it's in my pod's cache and on the "Discover" view 🤣 -- Whatcha working on / testing? 🤔
@duriny_test LOL! 😂 Pretty hard to ignore when it's in my pod's cache and on the "Discover" view 🤣 -- Whatcha working on / testing? 🤔
I'm creating a wrapper for the Yarn.Social API as a back end to twtr, so twtr users can use a yarn pod as a twtxt.txt host. Makes it easy to be able to tweet from the command line and the browser (and presumably the mobile app?) all at once :)
I hope you don't mind me creating an account on your pod? I do plan on removing the test tweets after myself once I'm done :)
@<~duriny https://envs.net/~duriny/twtxt.txt> Oh! That's bloody cool as shit 😎 😂 Nice one! 👌
This is more or less what I'd like the yarnc CLI itself to grow features for, maybe when you're done you can help me progress that? 🤔
@<~duriny https://envs.net/~duriny/twtxt.txt> Oh! That's bloody cool as shit 😎 😂 Nice one! 👌
This is more or less what I'd like the yarnc CLI itself to grow features for, maybe when you're done you can help me progress that? 🤔
For now I'm just planning on being able to choose a back end to twtr, e.g. a yarn pod, self hosting via ssh (like I am right now), maybe allowing hosting as a Github Gist, that sort of thing. I haven't taken a look at yarnc yet, but I might take a look now that you mention it :). I'm currently thinking of making the backend available as something like go get duriny.envs.sh/twtr/backend/yarn, but if you think yarnc might have some good overlap, maybe twtr can use go get Yarn.Social/go/api or something?
@<~duriny https://envs.net/~duriny/twtxt.txt> I _think_ it makes sense to use the API that's already available to you.
It's available here -- if it's worth splitting out into it's own sub-package and maybe giving it a nice vanity package URI like go.yarn.social/client we can do that 👌
@<~duriny https://envs.net/~duriny/twtxt.txt> I _think_ it makes sense to use the API that's already available to you.
It's available here -- if it's worth splitting out into it's own sub-package and maybe giving it a nice vanity package URI like go.yarn.social/client we can do that 👌