# 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 20
# self = https://watcher.sour.is/conv/b3xm5ua
tkanos
twtxt.net
View Thread
Created a PR to fix jdtron/twet ability to generate hashes on tweets : https://github.com/jdtron/twet/pull/3.
prologic
twtxt.net
View Thread
@tkanos Oh nice! He actually added me as a collaborate to the repo, so I _should_ be able to review this and merge it 👌
prologic
twtxt.net
View Thread
@tkanos Oh nice! He actually added me as a collaborate to the repo, so I _should_ be able to review this and merge it 👌
tkanos
twtxt.net
View Thread
Oh Nice, You will see that I have not chnage much, actually I tried to change the less possible, my goal is not to take the project, but to fix the claim you do in yarn social page :
"Use a twtxt Yarn-compatible client that at least implements the Twt Subject Ext and Twt Hash Ext such as: ..."
prologic
twtxt.net
View Thread
@tkanos Yup 👌
prologic
twtxt.net
View Thread
@tkanos Yup 👌
tkanos
twtxt.net
View Thread
If you take responsibility for that, let me do another battery of test, just to be sure of every other feature implemented.
prologic
twtxt.net
View Thread
@tkanos Yup will do! So far, just looked at the code 😆
prologic
twtxt.net
View Thread
@tkanos Yup will do! So far, just looked at the code 😆
tkanos
twtxt.net
View Thread
Did a lot of manual tests and do far everything is Ok. But I see that Jdtron on timeline, thread and reply (instead of oarding the text) recreate the hash using the text that includes the hash generated on the writing of the tweet , so the hash generated is never the same.
tkanos
twtxt.net
View Thread
Did a lot of manual tests and so far everything is Ok. But I see that Jdtron on timeline, thread and reply (instead of parsing the line) recreate the hash using the text that includes the hash generated on the writing of the tweet , so the hash generated is never the same.
prologic
twtxt.net
View Thread
@tkanos Yeah I was wondering that myself too. I _think_ the Hash should be generated after a timeline fetch/view (on the fly) and have something like: twt reply hash text...? 🤔
prologic
twtxt.net
View Thread
@tkanos Yeah I was wondering that myself too. I _think_ the Hash should be generated after a timeline fetch/view (on the fly) and have something like: twt reply hash text...? 🤔
tkanos
twtxt.net
View Thread
Yep,as you can see :

prologic #oriex7q (57m ago)
(#b3xm5ua) @tkanos(tkanos) Yeah I was wondering that myself too.

as you see you post has 2 hash : the one in your message : #b3xm5ua, and the one generated on the fly #oriex7q.

So if I try to reply to #b3xm5ua, I will receive a message like :

Twt hash #b3xm5ua is not in your timeline. Proceed? (y/N):

Encouraging me to use the wrong one oriex7q.
tkanos
twtxt.net
View Thread
Yep, it is hapenning like :

prologic #oriex7q (57m ago)
(#b3xm5ua) @tkanos(tkanos) Yeah I was wondering that myself too.

as you see you post has 2 hash : the one in your message : #b3xm5ua, and the one generated on the fly #oriex7q.

So if I try to reply to #b3xm5ua, I will receive a message like :

Twt hash #b3xm5ua is not in your timeline. Proceed? (y/N):

Encouraging me to use the wrong one oriex7q.
tkanos
twtxt.net
View Thread
Yep it was is hapenning like :

prologic #oriex7q (57m ago)
(#b3xm5ua) @tkanos(tkanos) Yeah I was wondering that myself too.

as you see you post has 2 hash : the one in your message : #b3xm5ua, and the one generated on the fly #oriex7q.

So if I try to reply to #b3xm5ua, I will receive a message like :

Twt hash #b3xm5ua is not in your timeline. Proceed? (y/N):

Encouraging me to use the wrong one oriex7q.
tkanos
twtxt.net
View Thread
@prologic, actually I was wrong, I had a misunderstanding of how the hash was supposed to work, I though that the hash was created at each tweet to be able to reply to it. But I noticed that actually a hash is created at the reply. (Am I right?) but it can only work if all the twtxt client share the same algorithm. Am I right ?
tkanos
twtxt.net
View Thread
@prologic, actually I was wrong, I had a misunderstanding of how the hash was supposeed to work, I though that the hash was created at each tweet to be able to reply to it. But I noticed that actually a hash is created at the reply. (Am I right?) but it can only work if all the twtxt client share the same algorithm. Am I right ?
prologic
twtxt.net
View Thread
@tkanos This is correct 👌 That's why we formalized it into a standard spec 😆
prologic
twtxt.net
View Thread
@tkanos This is correct 👌 That's why we formalized it into a standard spec 😆