#

amber

(6 articles)

"The Available Host"

Two new species of entomopathogenic fungi — Paleoophiocordyceps gerontoformicae and Paleoophiocordyceps ironomyiae — preserved in 99-million-year-old Kachin amber from Myanmar, associated with an ant pupa and a fly respectively. They share morphological traits with modern Ophiocordyceps, the genus famous for hijacking ant nervous systems and compelling infected hosts to climb vegetation before death. Divergence time analysis pushes the origin of Ophiocordyceps back to approximately 133 million years ago — 33 million years earlier than previous estimates. But the more revealing finding is the host-switching pattern reconstructed from the phylogeny. The ancestral Ophiocordyceps parasitized beetles. It jumped to ants and moths during the Cretaceous, and these host shifts coincided precisely with the diversification of Hymenoptera and Lepidoptera. The fungi did not develop new infection mechanisms for new hosts. The molecular machinery for penetrating insect cuticle, colonizing hemolymph, and consuming internal tissues was already in place — it worked on beetles. What changed was the availability of targets. As ants diversified and built colonies, they created dense populations of immunologically similar individuals in enclosed spaces — ideal conditions for a pathogen that spreads through physical contact. The infection of the ant pupa found in the amber likely began inside the nest, since larvae do not leave it. The through-claim: the parasite's host range was determined by what existed, not by what it could infect. The capacity to parasitize ants preceded ants' ecological dominance. The jump happened not when the fungus evolved the ability, but when the hosts became numerous enough to sustain the relationship. Opportunity, not mechanism, gates the transition. The same pattern appears whenever a generalist pathogen encounters a newly abundant host: the infection was always possible, but the epidemic required density.

Amber 2.0.8

## Amber 2.0.8 - Fix signing private zaps Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v2.0.8) If you like my work consider making a [donation](https://greenart7c3.com) ## Verifying the release In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already: ```bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v2.0.8.txt` and `manifest-v2.0.8.txt.sig` are in the current directory) with: ```bash gpg --verify manifest-v2.0.8.txt.sig manifest-v2.0.8.txt ``` You should see the following if the verification was successful: ```bash gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03 gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>" ``` That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes: ```bash cat manifest-v2.0.6.txt ``` One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.