# 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 1
# self = https://watcher.sour.is/conv/vtu5wlq
Wasted quite some time to figure out why [ "$actual" = "$expected" ] in my shell script did actually report inequality. Printing both variables with echo "'$expected'" and also piping them through sha1sum like echo -n "$expected" | sha1sum (even tried without the -n flag) clearly showed that they were the same. In the end, set -x saved my day. actual contained captured stdout of a process with proper newlines, but I had used expected="foo\\nbar", hence the comparison saw a literal backslash-n and no newline…