The paper you cited actually states that existing vaccines are less effective: “However, neutralization by 14 of the 17 most potent mAbs tested was reduced or abolished by either K417N, or E484K, or N501Y mutations.”
I had that thought, too. That’s the reason that stopped me from implementing sth like that.
I think a definitive solution to a cat-and-mice game would be an automated reverse-engineering of the chat apps.
I guess it’s only a matter of time until Facebook et al fight the bridges in form of lawsuits and API changes. Some years ago Facebook’s chat was accessible via the Jabber protocol. I think they won’t like users switching away from their apps and miss the control and ad revenue.
It doesn’t IIRC. But, you can combine it with ccache which can use a NFS share.
If you use clang, that might be of interest: https://github.com/yrnkrn/zapcc
Running it locally will always be faster as long as your machine is not a bottleneck (#cores, ram, ...). I think the use-case for distcc et al is to enable less-powerful machines to run builds faster by levering other machines. That’s exactly what we use it for at work. Our developers have not-so-powerful laptops and with distcc/icecc they can utilize the power of our build agents in the server room.
Have you though about using a pseudonym instead of your real identity for this? My contract even forbids me to contribute to OSS. You can’t advertise with any of your OSS work on your CV though.
I can confirm this. We had to install virus scanners on our self-driving car Linux boxes which are disconnected from any networks...
Fun part is that the AV scanner sometimes takes so much CPU time that the pedestrian detection algorithm fails and the car has an increased chances hitting them.