# 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 28
# self = https://watcher.sour.is/conv/6sur6eq
Just added support for custom themes to yarnd as a first-class "thing". Just point yarnd -t /path/to/theme and you're good to go π₯³
Just added support for custom themes to yarnd as a first-class "thing". Just point yarnd -t /path/to/theme and you're good to go π₯³
@prologic what is expected to be at /path/to/theme? A CSS? Name?
@adi I never assume. That's why I ask. Looking at the code, it looks like there are templates involved as well. Again, I will wait for @prologic on this.
@fastidious A whole copy of the default theme but modified π
@fastidious A whole copy of the default theme but modified π
@prologic so, a directory with βstaticβ and βtemplatesβ in it?
@fastidious Yup. Basically if you cp -a ./internal/theme /path/to/your_theme and modify to suit, you're good to go!
@fastidious Yup. Basically if you cp -a ./internal/theme /path/to/your_theme and modify to suit, you're good to go!
@prologic Works well π\n\nJust a note, I _did_ have to add the appropriate line in Makefile to also minify the CSS files in my custom theme folder, as obviously by default it will just process the default theme files.
@eldersnake Good point. This probably needs documenting? π€ One to add to the wiki? π€
@eldersnake Good point. This probably needs documenting? π€ One to add to the wiki? π€
eg:\n\nminify -b -o ./mytheme/static/css/twtxt.min.css ./mytheme/static/css/[0-9]*-*.css;
@prologic https://git.mills.io/yarnsocial/yarn/wiki/Using-Custom-Themes\n\nNot sure if it's better to just tell people to run the minify command manually instead of editing the Makefile or not. For mine that is kinda what a Makefile is for, but the next time the origin/HEAD version of it is modified the user will still have to merge/custom commit it π€ I'm probably overthinking this though.
@eldersnake Yeah it's probably better to avoid making local changes because that increase overhead of having to track upstream changes.
The thing is it doesn't actually really matter what tool you use to minify your static assets, just as long as you do because in production mode (non-debug, no -D) it will expect minified versions to exist.
Great work on the WIki page, first one! π π₯³
@eldersnake Yeah it's probably better to avoid making local changes because that increase overhead of having to track upstream changes.\n\nThe thing is it doesn't actually really matter what tool you use to minify your static assets, just as long as you do because in production mode (non-debug, no -D) it will expect minified versions to exist.\n\nGreat work on the WIki page, first one! π π₯³
@eldersnake Yeah it's probably better to avoid making local changes because that increase overhead of having to track upstream changes.
The thing is it doesn't actually really matter what tool you use to minify your static assets, just as long as you do because in production mode (non-debug, no -D) it will expect minified versions to exist.
Great work on the WIki page, first one! π π₯³
@prologic Yeah that makes sense. I removed the Makefile editing part now.
@eldersnake Cool π Might also be worthwhile mentioning you can use any valid CSS/JS minifier and link to a couple well known ones out there. The one the project uses is in fact written in Go (_I have a bias towards portable software and things written in Go π€£_)_
@eldersnake Cool π Might also be worthwhile mentioning you can use any valid CSS/JS minifier and link to a couple well known ones out there. The one the project uses is in fact written in Go (_I have a bias towards portable software and things written in Go π€£_)_
@prologic Yeah I guess my logic was anyone using yarnd is going to have that Go version of minify as it gets pulled down as part of make deps, but I guess I could link a couple other ones there. I've only ever used the Go one myself π
@eldersnake Not if they install the release binary or use the Docker image π€£
@eldersnake Not if they install the release binary or use the Docker image π€£