Hacker Newsnew | past | comments | ask | show | jobs | submit | yozel's commentslogin

Does that mean the people who got vaccinated won't benefit from a new vaccine, but unvaccinated people can?


Yes. And there is a small possibility that something even worse happens for those previously infected/vaccinated called antibody-dependent enhancement (ADE). ADE occurs when the antibodies generated during an immune response recognize and bind to a pathogen, but they are unable to prevent infection. Instead, these antibodies act as a “Trojan horse,” allowing the pathogen to get into cells and exacerbate the immune response.

The worst case with a new covid strain would be if people who were vaccinated by a previous vaccine or infected by an older strain experience antibody-dependent enhancement after being infected with the new strain. This is where the body recognized the new strain as the old and starts producing anti-bodies. These anti-bodies actually assist the new strain in infecting your cells, making the disease worse.

ADE has not been detected with any covid strains/vaccines so its not something to worry about for now but who knows what may happen in the future. I've been keeping my eye out for any news of ADE with any of these new strains.

Certain viruses like dengue fever can be much worse if you had previously caught a different strain due to ADE.

https://www.chop.edu/centers-programs/vaccine-education-cent...


Since the current vaccines are based on recognizing the spike protein, and since this South African (Nu?) variant has many mutations on the spike protein, what are the odds that a vaccinated person's immune system would recognize the mutated spike protein as being the same as the original one?


No idea. Time will tell but a high number of mutations is not ideal.


I'm not an expert at all, but I don't think viruses are mutually exclusive. Spread of the new strain can be fast and can became widespread, but can't decrease or affect the harmful one.


Why not use a normal HTTP proxy like Squid? It would be more easy to use it since almost all languages and clients support HTTP proxy built-in.


I evaluated Squid which was my first option, due to the existing code on the project I integrated the proxy, it wasn't that straightforward to interact with Squid.

I'm still thinking to use several Pies and it's simpler to evolve the custom-made proxy to support that, if you see the Github repo, it's pretty simple.

Last, getting a Scala project to run on the old Pi was a nice experiment worth trying.


This project should have the name "Stalin"


This will be a praise for him. Unfortunately censorship has become common practice around the world and it did not started with Stalin.


Most CoCs are like “Thou shalt not kill” or more like “Thou shalt be an asshole”. How is it even possible to not agree with that?


They go a bit further than that, for example the second result in Google for "open source code of conduct" is this one: https://www.contributor-covenant.org/version/2/0/code_of_con...

It includes things like:

* The use of sexualized language * insulting or derogatory comments * Other conduct which could reasonably be considered inappropriate in a professional setting

Obviously on the face of it these are extremely reasonable. The problem is that they are also extremely vague. Is it ok to say "fuck" in a comment? Or is that "sexualized language"? Can I say "this code is stupid" or is that too insulting? What if it isn't directed at anyone?

The fear is that there is a certain kind of person who loves picking people up over these sort of inconsequential rule ("social justice warriors"). For some reason they like to get into positions of power and then enforce petty rules.

I don't think that happens 99% of the time, but it does seem like CoCs encourage it and I've never seen evidence that extensive CoCs help so why bother? Just put a comment in your readme like you suggested - "CoC: Thou shalt not be an asshole."


Even if we agree with everything in your comment, the question is "Is the <1% of the time this happens a good enough reason the reject every project with a CoC?". Personally, I would answer no to this.


CoC's are inherently political, they say something about the people you have to deal with when contributing to the project. If you like that kind of people you'd see a CoC as a positive, but if you don't like them then you'd avoid CoC's. I don't see why this is so hard to understand.


You can always add additional Static IPs to Cloud NAT. The mail they sent doesn't mention any IP cost for Cloud NAT so I assume that it's free.


The point is, we don't need to know how exactly consciousness work to create an AGI. In theory, we can just simulate all the neurons in the brain on a supercomputer cluster and voila, we have AGI. Of course, it's not that simple but you get my point.


Facebook won't counter sue you. They don't have to. You just lose your right to use React, due to its license.


That's not true: https://code.facebook.com/pages/850928938376556

Facebook can't take away your rights to use React under the BSD license, no matter what you do.


I believe you still have a right to use it under copyright law since the license isn't terminated, it's just that potentially you may be infringing some patents, but so far nobody has actually pointed out what those patents would be, so I think it's a valid question.


You only lose the patent license, not the copyright license. So it is important to know if facebook actually owns patents covering react and if those patents cover other frameworks as well (e.g. because they cover all virtual DOMs).


What if quantum communication is a backdoor? Wireless, undetectable bugs!


I just need to store that 128-bit id to reach my 1-bit value. Well...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: