Upgrade overview This release contains upgrade notes that deviate from the norm: ℹ️ Requires assets recompilation For more information, view the complete release notes and scroll down to the upgrad...

On 2 May 2026, a cluster of passengers with severe respiratory illness aboard a cruise ship was reported to the World Health Organization. The ship is carrying 147 passengers and crew. As of 4 May 2026, seven cases (two laboratory confirmed cases of hantavirus and five suspected cases) have been identified, including three deaths, one critically ill patient and three individuals reporting mild symptoms. Illness onset occurred between 6 and 28 April 2026 and was characterized by fever, gastrointestinal symptoms, rapid progression to pneumonia, acute respiratory distress syndrome and shock. Further investigations are ongoing. The outbreak is being managed through coordinated international response, and includes in-depth investigations, case isolation and care, medical evacuation and laboratory investigations. Human hantavirus infection is primarily acquired through contact with the urine, faeces, or saliva of infected rodents. It is a rare but severe disease that can be deadly. Although uncommon, limited human to human transmission has been reported in previous outbreaks of Andes virus (a specific species of hantavirus). WHO currently assesses the risk to the global population from this event as low and will continue to monitor the epidemiological situation and update the risk assessment.

A conversation about "foreign entity of concern" rules with Jake Higdon and Isabel Munilla -- why they are needed and how Republicans are botching them.

2.54K Posts, 34 Following, 19.4K Followers · Straight-shooting information and analysis at the intersection of national security, law, and policy.

Happy Sunday! While you're enjoying a well-earned weekend, you might as well kick back and enjoy some more delightful tales of decentralized decadence from your favorite neighborhood pugs. Last week, we delivered _substantial_ performance improvements for ActivityPub in Ghost thanks to our long but necessary campaign to architect a solid database for all our Fediverse work. This week, we shipped a new feature! Dreams do come true. ## What's new with ActivityPub? Up until now it has been possible to publish new content into the Fediverse with Ghost, but.. um... it was sort of permanent. If you made a typo or just changed your mind about something, there was no way to delete. This week, we fixed that! You can now delete posts via ActivityPub. On the face of it, deleting a post sounds like a pretty unremarkable feature. If you can create a post, it follows that it should be straightforward to delete it – but distributed systems make things a little more interesting than centralized ones. In a regular application when you create something (most of the time) you're just adding a row to a database. When you delete it, you delete that row from the database. There's really not much to talk about. 0:00 /0:13 1× In a decentralized network, though, the question is: Which database? When you publish a post via ActivityPub it doesn't just get stored in 1 database, it gets sent out to every follower you have, and the server of every single one of your followers stores that post in _their_ database, too. If you want to delete a post, it has to be deleted in all those different places, too — and that doesn't just happen automatically. This is a relatively novel concept which hasn't been a significant feature of past decentralized protocols. If you send an email to 10,000 people, you can delete it from your email app's sent messages folder, but you can't delete it from anyone else's inbox. It's just... _out there_. In ActivityPub, though, it is possible. When you publish a post, you send out a `create` activity that instructs the servers of all the people who follow you to create a new post. Then, if you change your mind, you can also send out a `delete` activity which instructs all those same servers to delete a particular post. That's _outbound_ delete activity. You also need to be able to handle an _inbound_ delete activity, when someone else on another server sends a `delete` that they'd like you to process, to remove something you previously received from them. As of this week, Ghost can now handle both inbound and outbound deletes, so that they work properly across the whole Fediverse. 0:00 /0:45 1× Once you wrap your head around the core idea that everything in ActivityPub is an _activity_ which you send and receive, you begin to see how it's quite an elegant system for achieving a diverse set of functionality distributed across different applications. It's a different way of thinking about building software. It makes things a little more complex than they might be in an isolated system, but it's quite remarkable when you consider the scale of a functional decentralized network comprised of thousands of different pieces of software and millions of users, 99% of whom have never met, spoken, coordinated or interacted with one another. Just thinking about it makes my paws tingle. Anyway, that's all for this week. Next week, if all goes well, we'll have a larger update about the **public beta**.