Se puede cambiar el mundo | RT, follow & quote ≠ endorsement

Joined January 2009
1,618 Photos and videos
Pinned Tweet
[Thread of threads] #originsofSARSCoV2 #DRASTIC Compilation of relevant findings. Live thread. Let's start with the Addendum and the 7896 clade recently confirmed to come from the Mojiang mineshaft x.com/franciscodeasis/status…

[Thread] Addendum of WIV in Nature. What we know about the samples and the visits to the mineshaft of TG? TLDR: 7 trips: 4 already known (Ge et al., 2016), plus other 3 with massive sampling until 2015, including 7896-clade. All already in Latinne et al. (2020) #originsofSARSCoV2
6
68
144
Francisco de Asis retweeted
CIA whistleblower’s written testimony just dropped. It’s worth reading in full but here is the short version: By March 2021, before Biden’s 90-day COVID-origin review, FBI and DOE were already leaning towards lab origin. CIA analysts were leaning the same way, but CIA management didn’t like where the evidence was pointing and were actively obstructing their own people. Then, once the 90-day review kicked off in May 2021, Fauci personally fed the interagency team a curated list of experts. The same ones who wrote “Proximal Origin,” along with others, all part of the same ecosystem shaped by the same overlapping incentives. Basically, the same people involved in funding, defending, or advising on risky virological research were now tasked with assessing and informing official analyses on whether that research caused the pandemic. And then towards the end of the 90-day review period, someone at the CIA management flipped the agency’s assessment from lab-origin to non-consensus. Between 2022-2023, the bureaucratic ecosystem at CIA was stil working overtime to block its own analysts and technical experts. Internal emails even admitted analysts would have called a lab origin if management had let them. Not just that, the analysts who pushed back saw their careers wrecked. And those who buried it got promoted. All this comes from a career intelligence officer on Gabbard's DIG task force, the group literally tasked with declassifying COVID origins. His position gave him direct access to the documents and communications they were trying to hide. So why was the lab-leak conclusion resisted, delayed, and obscured for years? Groupthink. Political pressure. Fear of anything geopolitically inconvenient about China. Reluctance to implicate a research infrastructure funded for decades with American taxpayer money. Motives would be hard to prove, but the result was a textbook cover-up, intentional or otherwise. The real question now is whether Congress, DOJ and the powers that be will follow this wherever it leads.
I just sent a letter to @CIADirector asking him to personally review CIA whistleblower Jim Erdman’s written testimony from yesterday’s hearing. The CIA is on formal notice: there must be no retaliation against him for complying with a Senate subpoena. hsgac.senate.gov/wp-content/…
29
237
868
130,675
Si et al. (2024) Fig 3: the SARSr 7896-clade shows no HKU2 co-infections. But the same group previously published two HKU2 sequences (MN312322, MN312339) from this very clade. Their own data, quietly disappeared. sciencedirect.com/science/ar…
1
3
3
909
Francisco de Asis retweeted
Six years ago today, a truly shocking incident occurred that disgraces the name of science. A dozen scientists shared the view that Covid started with a laboratory experiment. So they met online to discuss how to mislead the world into thinking the opposite.
6 yrs ago today, on Feb 1, 2020, a group that included Anthony Fauci, Francis Collins, Jeremy Farrar, Eddie Holmes, Kristian Andersen, Robert Garry, Andrew Rambaut, Ron Fouchier, Marion Koopmans, and Christian Drosten came together to discuss how to mislead the public about the origin of SARS-CoV-2.
221
3,826
12,069
919,204
Francisco de Asis retweeted
Replying to @oscar_puente_
No aborda la cuestión planteada: soldadura entre viejo y nuevo con presumibles calidades y propiedades diferentes. Es saber popular desde hace más de 2 milenios que hay que tener mucho cuidado: "... porque lo nuevo tira de lo viejo y la rotura se hace más grande" (Mt 9, 17)
2
7
42
12,287
Adamuz – cronología aproximada (centrada en Alvia): 19:43 Impacto. 19:45 1ª llamada maquinista Iryo. Poco después: 2ª llamada Iryo 1ª llamada interventora Alvia (con brecha). 19:45–20:15 Probables llamadas pasajeros de ambos trenes al 112. Posible confusión en triangulación (dos ubicaciones a sólo ~570 m). ADIF no logra localizar al Alvia en pantalla ni contactar con maquinista. ~20:00 Primer contacto ADIF–112. 20:00 2ª llamada 112 a ADIF: ADIF informa de tren en Adamuz [Iryo] y "por lo visto" otro tren con heridos [Alvia]. 20:13 Tweet de ADIF informan descarrilamiento Alvia. ~20:25–20:35 1er aviso físico: pasajero Alvia [Galán] camina hasta el Iryo y avisa a GC: “hay otro tren”, causando sorpresa. ~20:35 Llegan 1os efectivos GC desde el norte (zona Iryo). ~20:40 La expedición AVLO (maquinista Miguel 1) llega al Alvia desde el sur tras caminar ~3 km por un túnel. 20:45–20:50 1er pequeño grupo de sanitarios [Marta] y bomberos llega al Alvia a pie (~570 m). 20:50–21:10 Llega Gonzalo con su quad, que rompe valla, siendo la única lanzadera improvisada de sanitarios y heridos. >21:10 Progresivo despliegue de servicios de emergencia (algunos testigos hablan de ~2 h para una respuesta plena). Inconsistencias: Las versiones oficiales que sostienen que la GC localizó visualmente el Alvia hacia ~20:15 entran en conflicto con múltiples testimonios que sugieren que el Alvia permaneció efectivamente “invisible” hasta ~20:40–20:50.
1
1
11
715
Por si es de utilidad:
2
232
Adamuz – tentative timeline (focus on assistance to the Alvia): 19:43 Impact. 19:45 1st call from Iryo driver. Shortly after: 2nd Iryo call 1st call from Alvia train attendant (head wound). 19:45–20:15 Probable passenger calls to 112 from both trains. Likely triangulation confusion (two locations only ~570 m apart). ADIF cannot locate Alvia on screen nor reach its driver. ~20:00 1st ADIF–112 contact. 20:00 2nd 112 to ADIF call: ADIF reports one train at Adamuz [Iryo] and “another one with injured passengers” [Alvia]. 20:13 ADIF tweet reporting Alvia derailment. ~20:25–20:35 1st physical alert: a passenger from Alvia [Galán] walks to the Iryo and tells GC “there is another train”, apparently causing surprise. ~20:35 First GC units arrive from the north (Iryo area). ~20:40 AVLO search party (driver Miguel 1) reaches Alvia from the south after walking ~3 km. 20:45–20:50 First small group of medics [Marta] firefighters reach Alvia on foot (~570 m). 20:50–21:10 Quad arrives, fence broken, sole improvised shuttle of medics and injured. >21:10 Gradual arrival of vehicles and full emergency deployment (some witnesses report ~2h for full response). Inconsistencies: Official claims that GC visually located the Alvia at ~20:15 conflict with multiple testimonies suggesting the Alvia remained effectively “invisible” until ~20:40–20:50.
9
14
1,936
Francisco de Asis retweeted
31 Dec 2025
There is an opportunity here to set an international precedent for sharing the genomic sequence of an outbreak pathogen ASAP. The 1st carcass was found on Nov 25 a few hundred meters from a lab working with ASF. It's been a month. The genomic sequence is still unpublished.
5
17
96
8,013
Brote PPA: - Desde el día 2 tienen la secuencia, y las compararon. - Dicen que sólo 2 mutations y 1 deletion vs FR682468 (Georgia/2007), pero no son "closely related". - Siguen sin publicar nada. Sólo un pequeño pantallazo. - Introducción por mediación humana, pero no saben cómo. A pocos metros un lab usando el propio FR682468. food.ec.europa.eu/horizontal…
El MAPA debería decirnos YA el porcentaje de coincidencia con el FR682468 de Pirbright lab. ncbi.nlm.nih.gov/nuccore/FR6…
3
9
19
11,065
La revisión de la secuencia Georgia/2007 en 2023 (FR682468.2 vs .1) corrigió sobre todo huecos (73 gaps en ~189 kb según BLAST). Incluso el genoma de referencia no es trivial de fijar.
1
2
348
Ocultan un dato clave: No indican si alguna cepa Georgia/2007 del CReSA comparte alguna de las 27 mutaciones detectadas. Si alguna cepa tuviera 2 ó más, sería game over, pues implicaría un MRCA dentro del CReSA posterior al FR682468 de Pirbright.
3
232
Brote PPA: Ya es tomadura de pelo. Siguen sin publicar las secuencias ni decir el porcentaje de coincidencia. "Solo la comparación exhaustiva del ADN de los virus de dentro y de fuera del laboratorio, que **todavía no ha terminado**, aclarará el origen del patógeno."
La auditoría al laboratorio señalado por la presunta fuga de la peste porcina deja todas las hipótesis abiertas. Estaría bien que @oscarordeig o el @CReSA_r explicaran con transparencia las mejoras que han propuesto los expertos externos: elpais.com/ciencia/2025-12-2… Con @LlanasSergi
8
8
1,041
Francisco de Asis retweeted
Descontrol en los laboratorios: cientos de accidentes exponen el riesgo catastrófico de fuga de patógenos peligrosos. "No son más que la punta del iceberg de los que realmente ocurren", alertó @XavierAbadMdG, ahora en el foco por la peste porcina africana elpais.com/ciencia/2025-12-1…
5
12
22
5,949
Francisco de Asis retweeted
Los @mossos y la @guardiacivil han ido a por muestras de los virus con los que trabaja el CReSA para ver si coincide con el de los jabalís infectados de peste porcina africana. Las muestras las recogen los especialistas de los Tedax. También solicitan documentos y clonan dispositivos elpais.com/espana/catalunya/…
3
16
28
16,831
Siguen sin publicar ningún metagenoma ni secuencia. Es una falta de transparencia injustificable habiendo tanto en juego. Ha hecho bien en intervenir la Justicia.
La Guardia Civil y los Mossos d’Esquadra acaban de entrar a registrar el laboratorio @CReSA_r, señalado como posible responsable de la fuga del virus de la peste porcina africana elpais.com/espana/catalunya/… Por @RebecaCarranco
4
15
892