> I’ve only had that problem trying to replay to a twt that was part of a thread.
I think I know what the problem is 🧐
# 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 235306 # self = https://watcher.sour.is?offset=232097 # next = https://watcher.sour.is?offset=232197 # prev = https://watcher.sour.is?offset=231997
wrong hashes
aka Lies
🤣 Also, If you chheck your own twt on twtxt.net, it looks like a root twt instead of a replay.
wrong hashes
aka Lies
🤣 Also, If you chheck your own twt on twtxt.net, it looks like a root twt instead of a replay.
s243lua
instead 🤷
s243lua
instead 🤷
!<nick url> ...
where url
is not your url.
$ bat https://twtxt.net/twt/vnr6wza | jq '.text'
"!<andros https://twtxt.andros.dev> U2FsdGVkX1/RU/NkTLRBrZGuZMaeIOoVkh7mBigVC/58DW80tKrwx1L3UCj0qWj8dvRU5/uwVh32ujJUr+O8ug=="
:z
PBKDF2_KEY_SIZE = 48
was the turning point! My dirty little crypt.class.php
can en- and decrypt, accoridng to the OpenSSL standard and options used in https://twtxt.dev/exts/direct-message.html
[ ↳ Reply to twt ]
button?
[ ↳ Reply to twt ]
button?