# 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 7
# self = https://watcher.sour.is/conv/msrnsya
Hmm I see it! It's so obvious 🤦♂️ I smell an attack of some kind.
Hmm I see it! It's so obvious 🤦♂️ I smell an attack of some kind.
@prologic To clarify, I meant some kind of a cache poisoning attack using the gossipping mechanism to inject garbage on purpose. Not hijacked user accounts.
However, since this all relates to bracketed text, I do not find an attack of some sort very likely. It's probably just a bug somewhere.
@lyse I'm not sure this is a bug to be honest? What possible code could cause this?! 🤔
@lyse I'm not sure this is a bug to be honest? What possible code could cause this?! 🤔
The reason I think this is some kind of attack is based on the repeated content and some of its uniqueness 🤔 This is so uncharacteristic if both victims 🤔
The reason I think this is some kind of attack is based on the repeated content and some of its uniqueness 🤔 This is so uncharacteristic if both victims 🤔