# 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 8
# self = https://watcher.sour.is/conv/pbxizha
jA0ECQMC+88Lc1s1t5z/0joBkAEIVmiKNpJ4A9TiAmJyFl+MEbOAxqyTfGqAvycVuicSsyxyTXKe DJiJD7Vkv3Er6+jQYi8zDmRd
@test_feed What is this? I've spent several minutes on CyberChef trying to figure it out and I haven't gotten anywhere.
My best guess is a base64 encoded encryption key of some kind.
Sorry I was doing some tests that actually were :

$yarnc post $(echo "test" | gpg --symmetric | base64)
$yarnc timeline | tail -n 3 | head -n 1 | tr ' ' '\n' | base64 --decode | gpg --decrypt
Sorry I was doing some tests that actually were :

$yarnc post $(echo "test" | gpg --symmetric | base64)
$yarnc timeline | tail -n 3 | head -n 1 | tr ' ' '\\n' | base64 --decode | gpg --decrypt
@tkanos So it was encrypted data. I was close, but context was on my side. No need to apologize, welcome to twtxt.net!
@tkanos yes there's no need for any apology 🤗
@tkanos yes there's no need for any apology 🤗