# 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 11
# self = https://watcher.sour.is/conv/vzksboq
Hmm, I just noticed that the feed template seems to be broken on your yarnd instance, @kat. Looking at your raw feed file (and your mates as well), line 6 reads:
# This is hosted by a Yarn.social pod yarn running yarnd ERSION@OMMIT go1.23.4
^^^^^^^^^^^^
Looks like the first letters of the version and commit got somehow chopped off. I've no idea what happened here, maybe @prologic knows something. :-? I'm not familiar with the templating, I just recall @xuu reporting in IRC the other day that he's also having great fun with his custom preamble from time to time.
That "broken" comment doesn't hurt anything, it's still a proper comment and hence ignored by clients. It's just odd, that's all.
@lyse This could just be a bugger Makefile or something. I'm not sure what version @kat built/deployed from? 🤔🤔 -- Also I need to release v2.0 soon™
@lyse This could just be a bugger Makefile or something. I'm not sure what version @kat built/deployed from? 🤔🤔 -- Also I need to release v2.0 soon™
@prologic so i did a mistake that i've done before and i think i just pulled from the main branch which is STUPID i KNOW and i don't LEARN but whatever. i was having trouble with my go version and the makefile so i think i literally just ran it as my user with go in the path and redirected the binaries to go to a temporary directory i made and then moved them to /usr/bin lol. i'm not sure what could've caused this! probably something in the pipeline of weirdness i just wrote out
@prologic so i did a mistake that i've done before and i think i just pulled from the main branch which is STUPID i KNOW and i don't LEARN but whatever. i was having trouble with my go version and the makefile so i think i literally just ran it as my user with go in the path and redirected the binaries to go to a temporary directory i made and then moved them to /usr/bin lol. i'm not sure what could've caused this! probably something in the pipeline of weirdness i just wrote out
@kat Building from source and from the main branch is totally fine. In fact encouraged. I have a philosophy of main being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
@kat Building from source and from the main branch is totally fine. In fact encouraged. I have a philosophy of main being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
Anyway... Sounds like there is a bug with the version logic. I'll see if I can fix it.
Anyway... Sounds like there is a bug with the version logic. I'll see if I can fix it.
@prologic ah that's good lol! i once pulled from main for a huge web app that i deployed and it haunts me because it will make upgrading so much harder lol
@prologic ah that's good lol! i once pulled from main for a huge web app that i deployed and it haunts me because it will make upgrading so much harder lol