One scenario -- Prizoghan was not actually on the plane, and this is a false-flag for him to disappear for a while.
a) Putin knows
b) Putin doesn't know
Scenario two -- Prizoghan was on the plane
a) It was an accident by low-level people
b) it was authorized by Putin or close cronies
No matter which of those it was, watch carefully what happens with Wagner forces in Africa, Syria, and Belarus. They are not likely to be happy about what happened. Unhappy, armed criminals are not a good thing.
NOT NOW EARTHQUAKE WE ARE HAVING A HURRICANE WAIT YOUR GODDAMN TURN
[Pointing fiercely at wildfires, riots]: AND YOU! FUCK RIGHT OFF
"What are your top 12 #programming books?"
Me: 🤔
Due to popular demand, here is a list of the fedi-services that are part of the infosec.* family:
1 - https://infosec.exchange - Glitch-soc fork of Mastodon (this instance does not block threads.net)
2 - https://relay.infosec.exchange - Activitypub relay
3 - https://video.infosec.exchange - Peertube instance (like youtube)
4 - https://infosec.press - WriteFreely blog*
5 - https://pixel.infosec.exchange - Pixelfed instance (like instagram)
6 - https://matrix.infosec.exchange - Synapse (with sliding sync) homeserver*
7 - https://infosec.place - Akkoma instance (like mastodon)
8 - https://infosec.town - iceshrimp instance (like mastodon)
9 - https://infosec.pub - Lemmy instance (like reddit)
10 - https://fedia.io - General interest mbin instance (also like reddit)
11 - https://fedia.social - General interst Iceshrimp instance
12 - https://elk.infosec.exchange - Elk web interface for Mastodon
13 - https://books.infosec.exchange - Bookworym instance (like goodreads)
14 - https://meetups.infosec.exchange (mobilizon)
15 - https://infosec.space - Glitch-soc fork of Mastodon (this instance does
block threads.net)
16 - https://convo.casa - Glitch-soc Mastodon instance
17 - https://ioc.exchange - Glitch-soc mastodon instance
*indicates the instance authenticates against Infosec.exchange