# 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 2
# self = https://watcher.sour.is/conv/y4zpgnq
I wonder, what's the current status of analyzing Go dependencies in general? Does one still require a diploma on that matter or got this any better in the meantime? → https://search.twtxt.net/search?q=%23jz6y7sa&t=term&f=conv&s=created&s=_id All I want to do is find out why some dependency is included, wether a certain dependency is a production or test dependency and things like that. I also see still lots of open general tickets, e.g. #46365, #42504, etc.
What tools or commands do you use?
Also, what's up with yarns? The link in @prologic's message doesn't show up in the "conversation view" in yarns (my first link). Yarns needs more love. :-)
Oh, that's very interesting! Pruning test dependencies from Go binaries. Gotta check our stuff at work tomorrow. I hope that we didn't mess up, I know of at least a couple of test packages we have for code reuse. Yarnd and yarns look alright in that regard. Just an hour ago I also learned go version -m $go_binary to find out which things ended up in the built binary, sweet.