# 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 7
# self = https://watcher.sour.is/conv/euoos2q
movq
www.uninformativ.de
View Thread
@david @andros The correct hash would be si4er3q. See https://twtxt.dev/exts/twt-hash.html, a timezone offset of +00:00 or -00:00 *must* be replaced by Z.

(That said, there’s a bug in jenny as well. It only replaces +00:00, not -00:00. 🤡)
movq
www.uninformativ.de
View Thread
@david @andros The correct hash would be si4er3q. See https://twtxt.dev/exts/twt-hash.html, a timezone offset of +00:00 or -00:00 *must* be replaced by Z.

(That said, there’s a bug in jenny as well. It only replaces +00:00, not -00:00. 🤡)
movq
www.uninformativ.de
View Thread
Scratch that, no bug in jenny. There’s actually a test case for this. Python normalizes -00:00 to +00:00, so the negative case never happens.
movq
www.uninformativ.de
View Thread
Scratch that, no bug in jenny. There’s actually a test case for this. Python normalizes -00:00 to +00:00, so the negative case never happens.
eapl.me
eapl.me
View Thread
just a note that we are doing that on PHP: https://github.com/eapl-gemugami/twtxt-php/blob/master/docs/03-hash-extension.md#php-72

That PHP snippet could be merged into https://twtxt.dev/exts/twt-hash.html
andros
twtxt.andros.dev
View Thread
@movq @aelaraji Yes @david It would be good for me, or new developers, if the documentation were agnostic. And if possible with many example cases. I'm fine-tuning the code as you inform me of bugs, trial and error. It's a lesson to be learned for the future.
andros
twtxt.andros.dev
View Thread
@movq @aelaraji Yes @david It would be good for me, or new developers, if the documentation were agnostic. And if possible with many example cases. I'm fine-tuning the code as you inform me of bugs, trial and error. It's a lesson to be learned for the future.