# 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/7fejx6q
prologic
twtxt.net
View Thread
Just a test to see if GIFs are now natively supported in yarnd, nothing to see here, move along 😅

prologic
twtxt.net
View Thread
Just a test to see if GIFs are now natively supported in yarnd, nothing to see here, move along 😅

eaplmx
twtxt.net
View Thread
@prologic haha, it's working here!
lyse
lyse.isobeef.org
View Thread
@prologic So I think there's a bug. The linked GIF in the feed is enlarged I think: https://twtxt.net/media/iujTqyVeq4wd3GwcRG3CyB.gif But if I append the ?full=1 query, the served GIF is smaller and also lacks the resize artifacts. https://twtxt.net/media/iujTqyVeq4wd3GwcRG3CyB.gif?full=1 Unless the ?full=1 logic was inverted today (haven't caught up on the backlog), this sounds like a bug to me, that full=1 produces reduced images. Maybe just a bug in GIF handling.=
prologic
twtxt.net
View Thread
@lyse Ahh this is possibly a bug in the GIF handling. But I'm getting rather tired now to go re-look at that new code. Maybe if you're feeling generous and up to it you could help out here? I _really_ want to invert the logic here and get rid of this ?full=1 altogether and just internally serve "Downscaled" versions to users of a pod based on their Users Preferences or Pod settings.
prologic
twtxt.net
View Thread
@lyse Ahh this is possibly a bug in the GIF handling. But I'm getting rather tired now to go re-look at that new code. Maybe if you're feeling generous and up to it you could help out here? I _really_ want to invert the logic here and get rid of this ?full=1 altogether and just internally serve "Downscaled" versions to users of a pod based on their Users Preferences or Pod settings.