# 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 31
# self = https://watcher.sour.is/conv/e2yyp6a
@prologic i'm looking to put up a public instance of twtxt as it's really a great system. i'm wanting to put it behind traefik, can you provide a link to this? the dockerhub instructions note an example for traefik but the github repo doesn't seem to exist any longer.
@infra7 @prologic should be clear that i plan to run my instance behind a v3 tor circuit as well as a clearnet version using traefik. i found the new repo by searching github for the twtxt.yml and have the compose setup exposing 8080/tcp. i link it to a tor service and it will work no problem, but when i click on my id or another person's the link goes to 127.0.0.1:8080. Any thoughts on this?
Likely either I'm not passing the ENV of base_url properly or it's a docker networking thing
@infra7 @prologic i found a traefik config and set it up with a tls wrapped endpoint and it's working for a clearnet domain. i'll need to figure out how to connect this to tor so users have the option of clearnet or tor
@infra7 Yes sure!
I migrated all my project off Gitjub (sorry!)
See git.mills.io/yarnsocial
@infra7 Yes sure!
I migrated all my project off Gitjub (sorry!)
See git.mills.io/yarnsocial
@infra7 Yes sure!\n\nI migrated all my project off Gitjub (sorry!)\n\nSee git.mills.io/yarnsocial
@infra7 Yeah you need to specify a correct base url
@infra7 Yeah you need to specify a correct base url
@prologic
Thank you. I found the repo and baked my own image. Traefik works no issue with normal label annotation (even works dropping into a k3s cluster). But the problem I'm facing is in regards to trying to use a v3 tor address as the base url.
Anytime I link twtwt to the tor hidden service container even if the service ports are mapped 80:8000 on tor to the service twtxt/etc I'll receive a bunch of errors
https://pad.nixnet.services/RjlFjAm3S1SxEGR56uSR9g?edit
@infra7 @prologic Totally realize this is likely out of scope for the project, but would love to make this work along all of my other services which have dual gateways for clearnet/tor. Any insight would be appreciated. At the time of the errors the base_url was set to that v3 onion address and i verified it was working pulling away your project.
Included a docker-compose sample if by chance you see something that I'm overlooking. Been down with the sickness this week so may be cognitively missing brain cells :-)
Overall amazing project!
@infra7 That paste looks like you're hitting DNS issues during feed cache fetching cycles.
@infra7 That paste looks like you're hitting DNS issues during feed cache fetching cycles.
@infra7 See my previous reply. If you still have no joy, let's jump on a conference call using my self-hosted (https://mett.mills.io) and I'll try to help you out in real time π
@infra7 See my previous reply. If you still have no joy, let's jump on a conference call using my self-hosted (https://mett.mills.io) and I'll try to help you out in real time π
@prologic great, will do a bit of digging. only thing i could think of is twtxt doesn't know how to resolve over tor (which is not a twtxt issue). i'll have a few looks and things and report back
@infra7 @prologic i realized the problem. yarnd container is not routing through tor nor using dns within tor service container to resolve v3 address. sounds like i might have to bake in a proxy. will experiment and report back. could be an optional flag if you want a pr.
@infra7 Let me know π€ I have no experience with Tor π
@infra7 Let me know π€ I have no experience with Tor π
@prologic so here's what i found. twtxt container expects normal clearnet v4/v6 networking and dns. so while it sits behind a tor service container and links, twtxt networking still reached out to clearnet and cannot resolve when doing post method. need to add a proxy of some sort inside container build to resolve this. experimenting as i'm a bit ill today
@infra7 anything I can on the backend side?
@infra7 anything I can on the backend side?
@infra7 Also wonβt this mean your pod will only be accessible on the Tor network? π€
@infra7 Also wonβt this mean your pod will only be accessible on the Tor network? π€
@prologic it will have a split setup reading from the same storage volume so it can be easily accessed via tor or clearnet gateways. just now circling back to this as i've had life get in the way. hoping to solve the puzzle today
@prologic @infra7 \n\n>hoping to solve the puzzle today\n\nAnd what's preventing you?
@prologic @infra7 \n\n>hoping to solve the puzzle today\n\nAnd what's preventing you?
@infra7 Look forward to seeing you solve this π€
@infra7 Look forward to seeing you solve this π€