# 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 12
# self = https://watcher.sour.is/conv/kr6624a
@darch this got me to thinking--since twt is a text-based format, it should be relatively straightforward to merge the history from one account into another. I haven't thought through the implications of that for threads/yarns or whatever, but at least at the level of the data format it's almost trivial to do. I wonder if that's something to explore?
@abucci Exactly, the twt hashes and hence conversations explode and fall apart. Other than that, merging feeds works fine. If we had defined twt hashing differently in regards to the url metadata field ("use lexically last found URL for hashing from now on" instead of "very first URL wins"), it would have been quite straight forward. But that change is incompatible.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)