# 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 6
# self = https://watcher.sour.is/conv/ovlagaa
@bender True, I'm just not sure we can have it both way? π€ I can turn smartypants off, but I do seem to recall you wanted it on π€£
@bender True, I'm just not sure we can have it both way? π€ I can turn smartypants off, but I do seem to recall you wanted it on π€£
@prologic no, no, I haven't said anything about turning of smartypants! That would be a step backwards, right? I mean, 1/4 is the way to represent a fraction, so its rendering is right spot on.
@prologic I'm not a yarnd user, so it doesn't matter a whole lot to me, but FWIW I'm not especially keen on changing how I format my twts to work around yarnd's quirks.
I wonder if this kind of postprocessing would fit better between composing (via yarnd's UI) and publishing. So, if a yarnd user types 1/4, it could get changed to ΒΌ in the twtxt.txt file for everyone to see, not just people reading through yarnd. But when I type 1/4, meaning first out of four, as a non-yarnd user, the meaning wouldn't get corrupted. I can always type ΒΌ directly if that's what I really intend.
(This twt might be easier to understand if you read it without any transformations :-P)
Anyway, again, I'm not a yarnd user, so do what you will, just know you might not be seeing exactly what I meant.