Human to human.

Its not only "blood and vomit", it is any bodily fluid, so you also have sweat, saliva, breast milk and semen.

So you therefore have bedding, clothing, or medical equipment soiled with infected fluids.

And preparation of the body after death.

In addition, delayed diagnosis is not uncommon.

Access to and adherence to infection control can easily be a problem.

So, in essence you have various routes to amplification of spread.

Regarding the open data— we do believe that anyone should be able to publish in the open, and building should be permissionless much like the web. But we don't think all data should be public, and clearly there is strong demand in the world for private spaces.

The community is working intently on bringing permissioned data to AT Protocol, and there are already several working examples out there illustrating different approaches. The head of protocol at Bluesky, where I also work, has been publishing his views on where permissioned data is heading: https://dholms.leaflet.pub/3mhj6bcqats2o

Note that this isn’t the Zaire ebolavirus. We’re still pinning down specifics.

So the best thing you can do for your career by far is simply to find some way, any way, to be able to work in the US.

> Why the "almost"? They are all monads (I suppose you meant list comprehensions)

Sort of. In the right language, with the right implementation, any of these can be monads. In practice, JavaScript Promises aren't quite monads, and everything in Rust is a bit complicated because we have things like FnOnce vs Fn, and so on. And even when Rust has something that's conceptually a monad, you can't actually "impl Monad" for it, because the type system isn't quite expressive enough.

In general I think it's mistake to accidentally implement something that's not quite an algebraic or categorical structure. This often means that your design is just a bit "off" of a much cleaner design. But sometimes, like in Rust, you know why you can't use the clean mathematical structure.