|
def visit_twitter_and_log_in
visit 'https://cards-dev.twitter.com/validator'
find('input.js-username-field').set(ENV['TWITTER_USERNAME'])
find('input.js-password-field').set(ENV['TWITTER_PASSWORD'])
click_on('Log in')
end
def enter_url_and_click_preview(url)
find('input.FormControl').set(url)
click_on('Preview card')
result = has_content?('Page fetched successfully')
visit 'https://cards-dev.twitter.com/validator'
end
end |
Q took it from here:
https://dev.to/ben/how-devto-dynamically-generates-social-images–2c2n
http://archive.is/wip/Jd2IA
(TinEye) Image first found on June 1st.
The Obama Foundation is the only place Tineye.com is showing it's published on.
Means -
The Obama Foundation are the only ones with this image.
Means -
The Obama Foundation created this image.
--> Obama org got the ball rolling after Floyd death with protest art, flyers and signage
The post "reconcile" was meant to signal to someone (investigators) that there's a link between Floyd and the Obama Foundation. The next post was meant to clarifiy to anons that the team knows perfectly how that shit works (and so they posted the code)
The tweet card updated because the site updated, however that is not what Q pointed to. Web developers frequently use the card validator privately BEFORE they update a page, to make sure the card looks proper before they go live.
What Q is saying is that:
1) they control Twitter, and
2) they saw the Obama web developers sent requests to validate the GEORGE FLOYD card BEFORE the Floyd event happened.
It's a warning - "we caught you"
MOAR on the script snippet Q posted:
browser automation, capibara, ruby
Confirmed.
From: https://dev.to/ben/how-devto-dynamically-generates-social-images–2c2n
"Twitter does not expose their cache-busting feature via API, so we had to ping it via browser automation.
It's a Ruby file which makes use of Capybara and Selenium to automate the process of pinging the Twitter card cache validation. It makes use of basically these three methods:"
SCREENSHOT: https://postimg.cc/mt2str2p |