I also wouldn't expect much from giving D3 in a hospital setting since it takes time for D3 supplementation to affect serum levels.
That's why the MATH+ protocol [1] recommends Calcifediol or Cholecalciferol. According to their own review [2] the protocol reduces hospital mortality from 20-30% to about 5%.
There are plenty of cofounders to consider, the biggest one might be the transition from innate to adaptive immunity (the latter potentially mistriggering as a cytokine storm).
Robert Gallo presented [1] an interesting idea to keep the innate system boosted by taking extra doses of a vaccine (he proposes using OPV). My pet corollary to Gallo's idea is that kids may have extended protection by having been more recently vaccinated (than adults).
It always bothers me when otherwise well-meaning educational materials are untested and completely miss major points they seem to be making.
Case in point, where it explains how to teach make to compile C files into object files, and then provides a rule to compile all files _from source_ rather than from object files.
# Tell make how to compile your *.c files into *.o files
%.o: %.c
gcc -c -o $@ $< $(CFLAGS)
# Finally, tell make how to build the whole project
final_binary.elf: $(SRCS)
gcc $(INCLUDE) $(CFLAGS) $(LFLAGS) $^ -o $@
This compiles the final binary from the sources, not using the object files and the rule above it.
(And clearly the leading example was never tested as it also missed the closing parentheses after "$(CFLAGS"!)
Anyway to take advantage of the c->object rule, the sources of last line should be changed to use files like this:
# Finally, tell make how to build the whole project
final_binary.elf: $(SRCS:.c=.o)
gcc $(INCLUDE) $(LFLAGS) $^ -o $@
To be pedantic, the above will recompile faster but will not necessarily be correct when header files change, so with that change it would be good to integrate automatic dependency generation [1] as well (for the object files).
Verizon claimed that the archivists violated the "terms of service" [1], but I couldn't find any reference to automation, downloading, crawling, or denial of service attacks that might apply.
Does anyone have an idea of exactly what term or terms were violated by the archivists?
Just playing a devil's advocate here. The way archivists are downloading the data can be said to disrupt the services, which is mentioned in the terms of service:
2. d. viii: "interfere with or disrupt the Services or servers, systems or networks connected to the Services in any way."
I'd also like to point out that the apparent spokesperson Brenda Fowler said in her open letter to Verizon, that "If the problem is that all our attempts to rescue our archives in the time we have left is causing an overload or strain on your servers, then stop making us HAVE to work around the clock, and GIVE US MORE TIME. ..." Probably not the wisest thing to say right now.
Also, archiving the groups with automated tools is against the Use of Services rule, that states the following:
2. e: "Use of Services. You must follow any guidelines or policies associated with the Services. You must not misuse or interfere with the Services or try to access them using a method other than the interface and the instructions that we provide. ..."
As I mentioned in another comment, I really support the cause and am a big fan of archiving myself but it's unfortunately quite clear that Verizon is right at calling out the violations of "terms of service".
Using the interface wouldn't block scrapers, yes? They do use the interface. But, this is academic I think. They offer a broken way to get our stuff, and say that we can't do anything else. Should we acquiesce to this?
As for bogging down the servers, my understanding was different from what the author said. They hadn't started to archive, but were in script testing mode and were accumulating yahoo accounts. What I saw of their activities, they were very careful about not overloading the servers. (I know that because I was backing up my own groups independently at the time, and I was able to do it. Luckily.)
Correct. They had done some testing, but that's all. They were just getting yahoo id's, while iterating on software improvements, so they could then download the groups.
In the old days prior to live-view, some even added the mirror back!
https://www.l-camera-forum.com/leica-wiki.en/index.php/Visof...