,
10 tweets,
7 min read
Read on Twitter
Different Twitter accounts love different things and when you're @ElectroWave, apparently most of those things are tweets from RT and Sputnik.
cc: @ZellaQuixote
cc: @ZellaQuixote
For folks who ain't RT and Sputnik, the tone of @ElectroWave's replies can be less friendly - this account has a fondness for threats both veiled and overt.
Other than professing love for RT/Sputnik reporting and threatening random Twitter users, what does @ElectroWave tweet about? Electronic music seems to have been the original focus, but pro-Kremlin tweets re Ukraine began in 2014, and things get more interesting from there. . .
Per @ElectroWave, the Treaty of Guadalupe is invalid and more than half of US territory actually belongs to Mexico or Russia. (Since Russia was uninvolved in the Treaty of Guadalupe, the latter may refer to the Alaska Purchase, but this is unclear from the account's tweets.)
The "half of the US belongs to Mexico/Russia" theme continues in @ElectroWave's repeated tweets. Tweets about recent events in Venezuela, awe at Russia's military capacity, and assertions that the USA = "terrorists" also evidently merit duplication.
Also among @ElectroWave's specialties: everything from the Sandy Hook shooting to the Skripal #Novichok poisoning is, of course, a #FalseFlag. To support these claims, @ElectroWave cites reporting from outlets such as Infowars, BeforeItsNews, and RT.
Speaking of RT, it and the LA Times (account claims to be based in Los Angeles) comprise the bulk of @ElectroWave's media links, with Infowars, BeforeItsNews, Sputnik, and the ironically-named "NoDisinfo" among the other frequent fliers.
The set of accounts @ElectroWave most frequently replies to mirrors its taste in news sources: the official English-language RT and Sputnik accounts are at the top of the list. Overall, 24 of the 30 accounts most frequently replied to are affiliated with media organizations.
(previous thread on NoDisinfo, for reference)
Someone should probably tell @ElectroWave to reply *before* blocking next time. . .
