Comment by ashwinpp

Comment by ashwinpp

I have a counterpoint for discussion against taking the flu vaccine based on the facts we know, and a two independent assumptions I make.

We know that influenza is different from other viruses because 1) There are many strains of influenza, it has a high mutation rate 2) Flu vaccines are based on a forecast of likely strains and typically cover only at most 50% of the strains in a given year [1]

Now let us make the following assumption - Actual flu infection boosts immunity after recovery from the infection compared to vaccination (perhaps an analogy would be how muscle recovery happens after microtears after a strength training workout with heavier weights).

In which case, one might conclude - Since a stronger immune response is great against a fast mutating virus and around 50% of strains are not covered by vaccines anyways, that the benefit of boosting immune response against future infections (beyond the current year) outweighs cost of getting infected and is a better choice than getting immunized against 50% of the strains with increased chances of getting flu due to the other 50% anyways

Assumption 2 - Getting exposed, but not infected by flu, increases the number of strains one's body is immune to. Something sort of like vaccination, but without taking the vaccines themselves.

For the purpose of modelling, let us also make the assumptions that all strains arise and propagate independently. That is the strains not covered by vaccination expose the same number of people unaffected by herd immunity, while the strains covered by the vaccination face herd immunity.

Now consider the strains covered by the vaccine, whose spread is reduced due to herd immunity. It is great for everyone vaccinated against the strains, but for people not vaccinated against it, it prevents exposure from and hence immunity. This might be a case where the utility of vaccination decreases for non-vaccinated individuals instead of increasing (herd immunity) as a function of the fraction of vaccinated population. In other words, the more people vaccinated for flu, the less likely an non-vaccinated person is to get exposed, the less likely is he/she to develop immunity towards those strains naturally. Thus this would prevent population level immunity from arising, where it would have arisen naturally.

Note that in this scenario, one might question that in the natural course of events, a certain percentage of population will develop immunity anyways and hence become equivalent to the scenario where some part of the population is vaccinated. However there are three major differences. First is that there is a certain delay between getting infected, spreading to others and gaining immunity. Thus for the same percentage of immune population, there might be larger population exposed in the natural course of events. Second is that many individuals might get infected, transmit and immunized to a strain without getting infected, thus such an individual gets all the benefits of vaccination, but might help others get exposed and immunized to a strain. And third that vaccination is more aligned with socio-economic factors while infection less so.

To conclude, if any of the two assumptions I state are true, then we should perhaps not blindly apply the same logic that applies to other viruses for which we have vaccinations.

[1] https://news.ycombinator.com/item?id=15562258

Replies ashwinpp · 2017-10-27
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.