Stories
Slash Boxes
Comments

SoylentNews is people

Another COVID-19 Reinfection: This Time Second Infection Was More Severe

posted by Fnord666 on Tuesday September 01 2020, @11:55AM   Printer-friendly
from the common-cold-/-covid-19? dept.

Freeman writes:

https://arstechnica.com/science/2020/08/another-covid-19-reinfection-this-time-second-infection-was-more-severe/

A 25-year-old resident of Reno, Nevada was infected with the pandemic coronavirus, SARS-CoV-2, two times, about 48-days apart, with the second infection causing a more severe case of COVID-19 than the first and requiring hospitalization and oxygen support.

That's according to a draft study, led by researchers at the University of Nevada and posted online. The study has not been published by a scientific journal and has not been peer-reviewed. Still, it drew quick attention from researchers, who have been examining data from the first confirmed case of a SARS-CoV-2 reinfection, reported earlier this week.
[...]
Amid the more than 24.5 million cases worldwide, it is completely expected to find some recovered patients who are not completely protected by their immune responses and are thus vulnerable to reinfection.

The big question is: how common is this scenario?

Original Submission

 
This discussion has been archived. No new comments can be posted.
Another COVID-19 Reinfection: This Time Second Infection Was More Severe | Log In/Create an Account | Top | 113 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by choose another one on Tuesday September 01 2020, @09:46PM (8 children)

    by choose another one (515) Subscriber Badge on Tuesday September 01 2020, @09:46PM (#1045109)

    Well that attempt to use gt / lt chars showed up different in preview to submitted, I swear, weird. Should have been:

    [less than] 1% die
    [greater than] 1% left with long term damage

    Just imagine the proper characters, one day I'll figure out how to get them to appear in a post.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 0) by Anonymous Coward on Wednesday September 02 2020, @06:46AM

    by Anonymous Coward on Wednesday September 02 2020, @06:46AM (#1045282)

    It's a trap.

    & lt (< if you take the space out) shows up fine in preview, but SN changes it in the input text field to the actual character when it displays the preview. This turns it into opening a tag. The way to get around it is to copy the entirety of what you typed in the text box, then do preview. If it's ok, empty the text box and then paste in what you copied.

  • (Score: 3, Informative) by The Mighty Buzzard on Wednesday September 02 2020, @03:34PM (6 children)

    by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Wednesday September 02 2020, @03:34PM (#1045426) Homepage Journal

    Use &lt; and &gt; and it should work fine. That's done intentionally to keep arbitrary tags from being a thing and to keep the balanceTags sub viable.

    --
    My rights don't end where your fear begins.

    • (Score: 2) by deimtee on Wednesday September 02 2020, @09:22PM (3 children)

      by deimtee (3272) on Wednesday September 02 2020, @09:22PM (#1045606) Journal

      Yeah, they work fine but preview changes them in the input box. You click preview, it looks fine, click submit, it's messed up unless you edited all the converted < and > back to the & codes.

      --
      If you cough while drinking cheap red wine it really cleans out your sinuses.

      • (Score: 2) by The Mighty Buzzard on Thursday September 03 2020, @04:44PM (2 children)

        by The Mighty Buzzard (18) Subscriber Badge <themightybuzzard@proton.me> on Thursday September 03 2020, @04:44PM (#1045916) Homepage Journal

        Nah, I checked on this very comment and properly written entities do in fact stay entities; exactly as you keyed them in. It's when you don't include the semi-colon that is most definitely part of any HTML entity that things go wonky. <see?>

        --
        My rights don't end where your fear begins.

        • (Score: 2) by deimtee on Saturday September 05 2020, @07:20PM (1 child)

          by deimtee (3272) on Saturday September 05 2020, @07:20PM (#1046921) Journal

          Ah. I am not much of an HTML weenie. They worked with just &lt and &gt so I just assumed that was the correct code and that it changing in the comment box was a bug.

          --
          If you cough while drinking cheap red wine it really cleans out your sinuses.

    • (Score: 3, Informative) by choose another one on Wednesday September 02 2020, @09:42PM (1 child)

      by choose another one (515) Subscriber Badge on Wednesday September 02 2020, @09:42PM (#1045616)

      Yeah, I knew I had to use the entities and thought I had, and checked it in preview...

      I have played around a bit and figured out what I did:

      - if you forget the semicolon (so use "&lt &gt")
      - and then use preview, it shows up "correct" (as expected if you had remembered the ; i.e. "< >" ) in the _preview_
      - BUT it also turns it into < > in the _comment_
      - so if you forget the semicolon, hit preview, check preview, and then submit, your posted comment is not like the preview

      Not sure if you consider that a bug or just an idiot user who hasn't edited raw html in a long time (and doesn't miss it). Hopefully I've actually got the html entities right this time so it makes sense...