# 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 22
# self = https://watcher.sour.is/conv/aej5m2q
win0err
kolesnikov.se
View Thread
@prologic (re: Just discovered ...) On the one hand, twtxt has become more popular thanks to Yarn.social. On the other hand, subject and hashtag extensions took away the simplicity of the protocol. For example, it is impossible to understand which conversation (#base32hash) a tweet refers to or to reply to a tweet without going to a yarn.social pod. Compare with re: in this tweet which can be written without using any client at all
prologic
twtxt.net
View Thread
@win0err Sorry I didn't see your -mention until now. So sorry for the late reply. The thing is pretty much every single extension was the formalisation of what was already happening in the ecosystem and community (which at the time was largely dead). -- The _only_ exception is the Twt Hash Extension (_which was also created by e member of the cummunity and the community agreed and we formalised that too_) in order to support "proper threading".

We generally have discussed as a community ideas of changing how this works, but we can never agree on why we should change it or how it would be better designed. I actually didn't come up with the design, some other very clever person did, and the thing is it gives us unique and interesting properties that clients can use for various display purposes that you cannot get any other way. Namely that each Twt and the calculated Hash are "content addressable".
prologic
twtxt.net
View Thread
@win0err Sorry I didn't see your -mention until now. So sorry for the late reply. The thing is pretty much every single extension was the formalisation of what was already happening in the ecosystem and community (which at the time was largely dead). -- The _only_ exception is the Twt Hash Extension (_which was also created by e member of the cummunity and the community agreed and we formalised that too_) in order to support "proper threading".

We generally have discussed as a community ideas of changing how this works, but we can never agree on why we should change it or how it would be better designed. I actually didn't come up with the design, some other very clever person did, and the thing is it gives us unique and interesting properties that clients can use for various display purposes that you cannot get any other way. Namely that each Twt and the calculated Hash are "content addressable".
prologic
twtxt.net
View Thread
@win0err Sorry I didn't see your -mention until now. So sorry for the late reply. The thing is pretty much every single extension was the formalisation of what was already happening in the ecosystem and community (which at the time was largely dead). -- The _only_ exception is the Twt Hash Extension (_which was also created by e member of the cummunity and the community agreed and we formalised that too_) in order to support "proper threading".

We generally have discussed as a community ideas of changing how this works, but we can never agree on why we should change it or how it would be better designed. I actually didn't come up with the design, some other very clever person did, and the thing is it gives us unique and interesting properties that clients can use for various display purposes that you cannot get any other way. Namely that each Twt and the calculated Hash are "content addressable".
prologic
twtxt.net
View Thread
@win0err Sorry I didn't see your -mention until now. So sorry for the late reply. The thing is pretty much every single extension was the formalisation of what was already happening in the ecosystem and community (which at the time was largely dead). -- The _only_ exception is the Twt Hash Extension (_which was also created by e member of the cummunity and the community agreed and we formalised that too_) in order to support "proper threading".

We generally have discussed as a community ideas of changing how this works, but we can never agree on why we should change it or how it would be better designed. I actually didn't come up with the design, some other very clever person did, and the thing is it gives us unique and interesting properties that clients can use for various display purposes that you cannot get any other way. Namely that each Twt and the calculated Hash are "content addressable".
prologic
twtxt.net
View Thread
@win0err So as long as you have a "decent client" (_for various definition of_) that has some kind of cache and/or long-term storage, you can easily use the same calculations and hash and form your own display of the same "threads" that can span many feeds.
prologic
twtxt.net
View Thread
@win0err So as long as you have a "decent client" (_for various definition of_) that has some kind of cache and/or long-term storage, you can easily use the same calculations and hash and form your own display of the same "threads" that can span many feeds.
prologic
twtxt.net
View Thread
@win0err So as long as you have a "decent client" (_for various definition of_) that has some kind of cache and/or long-term storage, you can easily use the same calculations and hash and form your own display of the same "threads" that can span many feeds.
prologic
twtxt.net
View Thread
@win0err So as long as you have a "decent client" (_for various definition of_) that has some kind of cache and/or long-term storage, you can easily use the same calculations and hash and form your own display of the same "threads" that can span many feeds.
prologic
twtxt.net
View Thread
For example jenny creates Maildir email threads out of them I believe and then you can use mutt to interact with your Twtxt feeds which then fully supports the Twt Hash and Twt Subject exts very nicely (and many Jenny uses do use Mutt).
prologic
twtxt.net
View Thread
For example jenny creates Maildir email threads out of them I believe and then you can use mutt to interact with your Twtxt feeds which then fully supports the Twt Hash and Twt Subject exts very nicely (and many Jenny uses do use Mutt).
prologic
twtxt.net
View Thread
For example jenny creates Maildir email threads out of them I believe and then you can use mutt to interact with your Twtxt feeds which then fully supports the Twt Hash and Twt Subject exts very nicely (and many Jenny uses do use Mutt).
prologic
twtxt.net
View Thread
For example jenny creates Maildir email threads out of them I believe and then you can use mutt to interact with your Twtxt feeds which then fully supports the Twt Hash and Twt Subject exts very nicely (and many Jenny uses do use Mutt).
win0err
kolesnikov.se
View Thread
@prologic: I understand the benefits of using hashes, it's much easier to implement client applications (at the expense of ease of use without the proper client). I must say that I like the way the metadata extension is done. Simple and elegant! It's hard to design simple things!
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
@win0err Yeah, fair. I should probably mention (if not already obvious) by just preserving the already-existing subject hash, its pretty easy to participate in a thread (assuming the same folks follow your feed). But yeah without a client its a. bit harder I suppose, one of the reasons we added a hash sub-command to the yarnc command-line tool/client.


  $ yarnc hash -u https://twtxt.net/user/prologic/twtxt.txt -t 2020-07-18T12:39:52Z "Hello World! 😊"
  o6dsrga
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅
prologic
twtxt.net
View Thread
Which btw is my first ever Twt: https://twtxt.net/twt/o6dsrga 😅