# 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 24
# self = https://watcher.sour.is/conv/6wgtdyq
@prologic How did you find that? xD Yeah only just connected up the domain. I have the certs, but thing I can't wrap my head around is using SSL certs with yarn on port 8000. 443 is tied up with my website.
@eldersnake Stick a load balancer in front and terminate TLS there. NGINX, Caddy, Traefik, etc.
@eldersnake Stick a load balancer in front and terminate TLS there. NGINX, Caddy, Traefik, etc.
yarnd itself has no builtin support for listening on a TLS port, I _coudl_ add it but it's not usually how I run things myself, I normally put a load balancer in front of things and terminate TLS there, it's far easier to manage.
yarnd itself has no builtin support for listening on a TLS port, I _coudl_ add it but it's not usually how I run things myself, I normally put a load balancer in front of things and terminate TLS there, it's far easier to manage.
@prologic All good, a quick NGINX reverse proxy did the job (that side of things is still new to me, but remarkably simple to configure it seems). In _theory_, it's working fine now.
@eldersnake @prologic If it goes down at anytime now it'll simply be the rate limiting, which I'll work on over time. Shouldn't happen often, and I could technically mitigate it a bit by scheduling Pagekite to restart every so often, but not ideal.
@eldersnake Ahh awesome! 👌 The _only_ problem of course is I can't follow a person by the same "nick" with two different feed sources 😂 So... Are you planning on migrating/moving your feed to your pod? I wonder if I should build a feature for this? 🤔
@eldersnake Ahh awesome! 👌 The _only_ problem of course is I can't follow a person by the same "nick" with two different feed sources 😂 So... Are you planning on migrating/moving your feed to your pod? I wonder if I should build a feature for this? 🤔
@eldersnake I _think_ it is working now too as I'm following your need feed 🥳
@eldersnake I _think_ it is working now too as I'm following your need feed 🥳
@prologic Ahh! I didn't even think of that problem. I was planning to. I did even have my feed copied over, but deleted it because I realised anyone following both would have doubled up posts. What's the best course here you reckon?
@eldersnake Yup no problems! 👌 It doesn't _matter_ too much if your pod is inaccessible at times, the whole point of decentralised software is to tolerate such things 😂
@eldersnake Yup no problems! 👌 It doesn't _matter_ too much if your pod is inaccessible at times, the whole point of decentralised software is to tolerate such things 😂
@prologic Ha, neat. So the same nicks aren't a problem?
@prologic Yeah agreed. 😀 Well I must admit that wasn't too difficult. Raspbian (or Raspberry Pi OS as they call it now...), even upgraded to _Bullseye_, only had golang 1.15, which doesn't have _embed_ which yarn needed, but once I pulled golang 1.17 from the Go site, no prob
@eldersnake Well they are, as-in I can't follow both feed at once with the same name ;)
@eldersnake Well they are, as-in I can't follow both feed at once with the same name ;)
@prologic Is it easy enough to change a nick once the account already exists? Although I mean I suppose ultimately I can get people to change over like you did (unfollow, follow new feed) and archive my old feed.
@eldersnake No for the moment unfollow and refollow is is the easiest way
@eldersnake No for the moment unfollow and refollow is is the easiest way
