ryan.staticnoi.se
investigative reporter / OSINTer (english-language editor @crimew.gay, contributor @geoconfirmed.org @virtualstreets.org etc.)
ey/they/it/any
give me tips/contact me on signal: rhinozz.1337
my previous work: https://muckrack.com/ryan-fae/portfolio/list
604 posts
2,489 followers
463 following
Regular Contributor
Active Commenter
comment in response to
post
that brevity of that was expected from the 6:51 lid but shit!
comment in response to
post
"tomraaow" is glorious
comment in response to
post
fantastic segment!
comment in response to
post
the GHSA is live.
"Using the /locales/locale.json with the locale and namespace query parameters, a malicious actor is able to execute arbitrary code, without being authenticated."
github.com/pterodactyl/...
comment in response to
post
patch commit here: github.com/pterodactyl/...
comment in response to
post
announce it loudly and do nothing about it
comment in response to
post
Sotomayor is reading from her dissent from the bench.
comment in response to
post
maybe you are right
comment in response to
post
ugh
comment in response to
post
what diplomacy
comment in response to
post
one can only hope. also should be more on friday if not
comment in response to
post
more than 35 thousand geotagged panoramas, on the Internet Archive. archive.org/details/cart...
comment in response to
post
alas, when we (speaking for all journos covering politics) get leaked information/media/etc., there is an obligation to protect those sources. that often means no attribution nor context. i apologize if the anonymous sourcing is so difficult to trust. (it is for us, too.)
comment in response to
post
agree!
comment in response to
post
geez, "sincerely" twice in a 45-word post. need to go back to my editing 101 course
comment in response to
post
bsky.app/profile/ryan... FYI, the screenshot Mira shared is authentic. this isn't intended to be a dunk, just an update for you, and i sincerely don't want hostility here from either of us (or anyone else in this thread). i sincerely apologize if it came off that way
comment in response to
post
cc @thefreeradical.org: an FBI release confirms this video is authentic.
www.fbi.gov/wanted/law-e...
comment in response to
post
not to speak on Mira's behalf here, but "where did you get this photo?" to an image obtained by a journalist, presumably under terms of anonymity, is a question that will not be answered. (also: police have not released information about their lead suspect. it was leaked to the Post.)
comment in response to
post
image from Google Street view, ca. April 25, 2024.
comment in response to
post
from another angle. note the outdoor power outlet boxed in cyan, which is also visible. shadows on the security camera image make it difficult to see that the wall is made of siding, not concrete.
comment in response to
post
Travis Akers on twitter claims that "sources on the ground" do not corroborate the initial claims of an attack on the embassy.
comment in response to
post
misinfo to look out for: the ResistanceTrench telegram channel, which has been highly reposted, claimed at 23:14 UTC that an "Associated Press report" says that "American fighter jets have entered Iranian airspace." this is incorrect. no such article exists.
comment in response to
post
note that three hours prior, reported at 19:43 UTC, the US Embassy in Baghdad told Julian Bechocha of @rudawenglish.bsky.social this:
> The Embassy and Consulate General remain open and operating.
comment in response to
post
note that as far as i can tell, it comes from an OSINT-community rumor
22:45 UTC: a rumor spreads around telegram ("Air raid sirens sounded in and around the US embassy in Baghdad's Green Zone.")
22:53 UTC: first twitter summarization claiming a "direct attack"
~23:08 UTC: Channel 12 repeats it
comment in response to
post
notable hearsay, and we'll see how it develops, but keep your eyes on it
comment in response to
post
hbd!!!
comment in response to
post
i was so fucking scared
comment in response to
post
update for anyone curious, not official but based off what we saw:
1) looks like a GCP change broke a bunch of their stuff
2) CF workers relied on GCP for their compute so they die
3) CF CDN dies
4) CF does *something* to mitigate the workers while GCP is restoring
5) GCP fixes whatever they broke
comment in response to
post
yeah, shit. guess i'll see when someone on hacker news recaps in two hours lol