Deutsch   English   Français   Italiano  
<v88i1m$id3f$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!3.eu.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!feeds.news.ox.ac.uk!news.ox.ac.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!news.eyrie.org!beagle.ediacara.org!.POSTED.beagle.ediacara.org!not-for-mail
From: RonO <rokimoto557@gmail.com>
Newsgroups: talk.origins
Subject: Re: Defective dairy H5N1 virus test
Date: Mon, 29 Jul 2024 12:03:50 -0500
Organization: A noiseless patient Spider
Lines: 56
Sender: to%beagle.ediacara.org
Approved: moderator@beagle.ediacara.org
Message-ID: <v88i1m$id3f$1@dont-email.me>
References: <v82saj$3d9pe$1@dont-email.me>
Reply-To: rokimoto557@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: beagle.ediacara.org; posting-host="beagle.ediacara.org:3.132.105.89";
	logging-data="94669"; mail-complaints-to="usenet@beagle.ediacara.org"
User-Agent: Mozilla Thunderbird
To: talk-origins@moderators.isc.org
Cancel-Lock: sha1:KW8UwfSip8Vh67h4xlQXa4oD9zk=
Return-Path: <news@eternal-september.org>
X-Original-To: talk-origins@ediacara.org
Delivered-To: talk-origins@ediacara.org
	id 81DBA229782; Mon, 29 Jul 2024 13:03:27 -0400 (EDT)
	by beagle.ediacara.org (Postfix) with ESMTP id 57B5B229765
	for <talk-origins@ediacara.org>; Mon, 29 Jul 2024 13:03:25 -0400 (EDT)
	id 165025DC55; Mon, 29 Jul 2024 17:03:55 +0000 (UTC)
Delivered-To: talk-origins@moderators.isc.org
	by mod-relay-1.kamens.us (Postfix) with ESMTPS id EA1FA5DC29
	for <talk-origins@moderators.isc.org>; Mon, 29 Jul 2024 17:03:54 +0000 (UTC)
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256)
	(No client certificate requested)
	by smtp.eternal-september.org (Postfix) with ESMTPS id 4896C5F824
	for <talk-origins@moderators.isc.org>; Mon, 29 Jul 2024 17:03:51 +0000 (UTC)
Authentication-Results: name/4896C5F824; dmarc=fail (p=none dis=none) header.from=gmail.com
	id CDBD5DC01A9; Mon, 29 Jul 2024 19:03:50 +0200 (CEST)
X-Injection-Date: Mon, 29 Jul 2024 19:03:50 +0200 (CEST)
X-Auth-Sender: U2FsdGVkX1+Q+DA+58AvJ/U27Y0yryNJiLhqW7Ycxqw=
Content-Language: en-US
In-Reply-To: <v82saj$3d9pe$1@dont-email.me>
	FORGED_GMAIL_RCVD,FORGED_MUA_MOZILLA,FREEMAIL_FORGED_FROMDOMAIN,
	FREEMAIL_FROM,FREEMAIL_REPLYTO_END_DIGIT,HEADER_FROM_DIFFERENT_DOMAINS,
	NML_ADSP_CUSTOM_MED,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no
	autolearn_force=no version=3.4.6
	smtp.eternal-september.org
Bytes: 5790

On 7/27/2024 8:22 AM, RonO wrote:
> https://www.scientificamerican.com/article/the-cdcs-test-for-bird-flu-works-but-it-has-issues/
> 
> Apparently the CDC admitted last week to congress that the test that 
> they first distrubuted to detect the dairy virus was defective.  They 
> claim that it wasn't their fault, but that the company that they 
> contracted to make the test screwed up on one of the H5 tests.  At this 
> point they are still trying to get the company to rectify their error 
> and create fully functional test kits.  It turns out that they have been 
> working with the defective test for months.
> 
> It could be one of the reasons that they never started wide spread 
> testing for the virus, though they do not make that claim.
> 
> The Scientific American article notes how something similar occurred at 
> the start of Covid when the CDC produced a defective test that held up 
> getting the virus under control.  This time the CDC claims that it 
> wasn't their fault, but it likely is their fault that they didn't 
> immediately get another company to make a functional test kit instead of 
> waste months trying to get the contract company to fix their mistake. 
> The article indicates that they are pretty sure that the company will 
> make fully functional test kits soon.
> 
> Ron Okimoto
> 

https://www.sfchronicle.com/health/article/h5n1-bird-flu-california-impact-19592660.php

Chronicle article on H5N1.  They claim that H5N1 is showing up in 
poultry in the bay area.  For some reason they are not testing dairy 
herds in California.  They know that multiple counties in the bay area 
show elevated levels of influenza in their waste water and that this is 
correlated with infected dairy herds in other states.  When I looked 
into this back in May I suspected that the Dairy Influenza likely first 
infected dairy cattle in California.  Poultry farms began to go down 
with H5N1 in central California dairy counties in October when they 
thought that the infection first started in Dairy cattle.  Poultry farms 
start to go down in states with infected dairy herds because of the 
crossover with Dairy workers and their close contacts also working at 
poultry farms.  In the Bay area commercial Poultry farms started to go 
down in October 2023 and it spread North to encircle the Bay Area 
(counties showing influenza in waste water were among the counties with 
infected flocks).  The Dairy virus has been found to be most closely 
related to a virus isolated from a Peregrine falcon in California.

I tried to get the sequencing results for the Poultry flocks, but I was 
told that the USDA did not release information on people involved in 
collecting and testing the California samples.  I could not contact 
anyone that would know what the sequencing results were.  The California 
sequences have not been included in any of the sequence analysis to 
date.  My guess is that they will find infected herds in California 
because the virus likely hasn't burned through all the herds at this 
time, and they will find that the initial infection predates the Texas 
samples and that the Texas virus likely came from California.

Ron Okimoto