# 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 9
# self = https://watcher.sour.is/conv/zogbtrq
@lyse I don't think this is true.
@lyse I don't think this is true.
@lyse yeah, tell us, @prologic, what isn't true? 🤔 You can't just go around, "that's not true, and that's not true; and that, and that!" without spelling out exactly what isn't, and why? For the love of god, why?! 😂
@lyse yeah, tell us, @prologic, what isn't true? 🤔 You can't just go around, "that's not true, and that's not true; and that, and that!" without spelling out exactly what isn't, and why? For the love of god, why?! 😂
Ah, and now he is "conveniently" sleeping. How, well, convenient! LOL.
Ah, and now he is "conveniently" sleeping. How, well, convenient! LOL.
LOL 😂 This:
> anyone could claim that some feed contained a certain message which was then removed again by just creating the hash over the fake message in said feed and invented timestamp themselves
I'd like to see a step-by-step reproduction of this. I don't buy it 🤣
Admittedly yarnd had a few implementation security bugs, but I'm not sure this is actually possible, unless I'm missing something? 🤔
LOL 😂 This:
> anyone could claim that some feed contained a certain message which was then removed again by just creating the hash over the fake message in said feed and invented timestamp themselves
I'd like to see a step-by-step reproduction of this. I don't buy it 🤣
Admittedly yarnd had a few implementation security bugs, but I'm not sure this is actually possible, unless I'm missing something? 🤔