# 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 16
# self = https://watcher.sour.is/conv/wa4iupa
@prologic looks like when I tap the hash from Goryon I am taken to the right place in the twtxt.net. Did you fix the issue? seems like it is working
@prologic looks like when I tap the hash from Goryon I am taken to the right place in the twtxt.net. Did you fix the issue? seems like it is working
@antonio No not yet, this is another example that is exhibiting this bug. I have a unit test that shows the failure, just trying to work out what the problem is, then I'll put up a PR :D
@antonio No not yet, this is another example that is exhibiting this bug. I have a unit test that shows the failure, just trying to work out what the problem is, then I'll put up a PR :D
@antonio No not yet, this is another example that is exhibiting this bug. I have a unit test that shows the failure, just trying to work out what the problem is, then I'll put up a PR :D
@antonio I tested this locally where I artificially edited a reply to a conversation to include the URI form of the Hashed Subject and it looks like is is actually fixed! 🎉 📷 
@antonio I tested this locally where I artificially edited a reply to a conversation to include the URI form of the Hashed Subject and it looks like is is actually fixed! 🎉 📷
@antonio I tested this locally where I artificially edited a reply to a conversation to include the URI form of the Hashed Subject and it looks like is is actually fixed! 🎉 📷