# 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 21
# self = https://watcher.sour.is/conv/qzhrlba
@jlj Your redirect on twtxt.net is missing the /twtxt.txt. :-) Don't you want to add TLS support, now that you're moving? Since people move around lately, I need to add a "mark all twts read" option to my client, because all the hashes are now different and show up again as unread.
@lyse Thanks for the heads-up! The redirect is fixed. On TLS, I think I got a bit confused: @prologic said something about twtd only speaking HTTP, and I sort of put certificates out of my mind after that. But can I just terminate the tunnel at my reverse proxy instead?
@lyse Thanks for the heads-up! The redirect is fixed. On TLS, I think I got a bit confused: @prologic said something about twtd only speaking HTTP, and I sort of put certificates out of my mind after that. But can I just terminate the tunnel at my reverse proxy instead?
@jlj Excellent! ;-) Yep, just let Nginx terminate the HTTPS session and pass everything over HTTP to twtd.
@lyse Right, that's now top priority in my twt project, in Taskwarrior. Cheers! (One idle search later) Ooo, turns out they just released a new version of task! :-D
@lyse Right, that's now top priority in my twt project, in Taskwarrior. Cheers! (%@t(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference) Ooo, turns out they just released a new version of task! :-D=
@lyse @thewismit Configuring the reverse proxy with certbot seems fairly straightforward, but I too am confused, around how twtd integrates, without changing $BASE_URL too, in my case.
@lyse @thewismit Configuring the reverse proxy with certbot seems fairly straightforward, but I too am confused, around how twtd integrates, without changing $BASE_URL too, in my case.
@thewismit\n\n> I don’t quite follow. What are the steps to redirect? I’m going to be changing my domain soon :)\n\nBasically its just a convention, a "letting us know" type thing. I wouldn't worry about it too much, as pods trigger an internal @twtxt FOLLOW event anyway, so the moment you change your pod's domain and base url we'll know about it as it'll come from a different URI and re-trigger the FOLLOW event.
@thewismit\n\n> I don’t quite follow. What are the steps to redirect? I’m going to be changing my domain soon :)\n\nBasically its just a convention, a "letting us know" type thing. I wouldn't worry about it too much, as pods trigger an internal @twtxt FOLLOW event anyway, so the moment you change your pod's domain and base url we'll know about it as it'll come from a different URI and re-trigger the FOLLOW event.
@thewismit
> I don’t quite follow. What are the steps to redirect? I’m going to be changing my domain soon :)
Basically its just a convention, a "letting us know" type thing. I wouldn't worry about it too much, as pods trigger an internal @twtxt FOLLOW event anyway, so the moment you change your pod's domain and base url we'll know about it as it'll come from a different URI and re-trigger the FOLLOW event.
@thewismit
> I don’t quite follow. What are the steps to redirect? I’m going to be changing my domain soon :)
Basically its just a convention, a "letting us know" type thing. I wouldn't worry about it too much, as pods trigger an internal @twtxt FOLLOW event anyway, so the moment you change your pod's domain and base url we'll know about it as it'll come from a different URI and re-trigger the FOLLOW event.
@jlj You _must_ change your BASE_URL or -u/--base-url at that point.
@jlj You _must_ change your BASE_URL or -u/--base-url at that point.
@jlj You _must_ change your BASE_URL or -u/--base-url at that point.
@prologic Ah, OK, that makes more sense. (%@t(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference) So, that means all outgoing connections from the pod are unencrypted, right? It can't initiate a TLS connection? Just browsers and twtxt clients to it?=
@prologic Ah, OK, that makes more sense. (Hamster furiously working...) So, that means all outgoing connections from the pod are unencrypted, right? It can't initiate a TLS connection? Just browsers and twtxt clients to it?
@jlj Outgoing connections use whatever scheme is defined by your following URLs
@jlj Outgoing connections use whatever scheme is defined by your following URLs
@jlj Outgoing connections use whatever scheme is defined by your following URLs