# 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/ugq2bpq
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?
@prologic I was actually thinking about starting tt from scratch in Go a couple of times over the years. But it's a hell lot of work. Not sure yet whether I really want to do that. And I would lose all my work on my parser, but oh well. Switching to Jenny and Mutt seems more realistic. I never tried any of the two, but it sounds extremly appealing. The only disadvantage of Mutt to me seems to be this explicit opening of a longer twt because the subject is limited in length. I reckon I would miss that from tt. No idea, though, again, I never gave it a try yet.
@lyse I like the idea that you are still using the original client as a backend and tt is just a frontend. And would like to be able to use it one day
but I do get that you want to build something better
@darch Yes, in the current state this tt is totally useless to everybody else. :-/ Still a lot of work required.
Thanks for clarifying, I'm now only following you on your own server. :-)
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests 😅 Then eventually replace what yarnd uses too 👌
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests 😅 Then eventually replace what yarnd uses too 👌
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests 😅 Then eventually replace what yarnd uses too 👌
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests 😅 Then eventually replace what yarnd uses too 👌