Not sure about the Recife protocol, but it's pretty much accepted now that the Milwaukee protocol doesn't work[1][2] - the initial case may have been some other encephalitis mimicking rabies.
Since you cannot forge the CF-Worker header in API requests (this header is added by Cloudflare's back end), it is not possible to send email for any domain that hasn't been locked down to your specific Worker.
I understand where you're coming from here, but the whole point of this article is at the 4-line solution is wrong (and the author specifically mentioned that every other answer on the stack overflow post was wrong in the same way as well). "Seemingly-simple problem where every naïve solution contains a subtle bug" is exactly the right use case for a well-designed library method.
But in a completely benign way. I question why a few edge cases of writing 1000kb instead of 1Mb—so not even a misrepresentation—would ever be worth the code bloat. This is about making stuff slightly more convenient to read.
I agree with you— that was a lot of drumming for what turned out to be kind of a nothingburger as far as the "bug".
At the same time, putting this kind of thing in a library (or even a language's stdlib) is worthwhile for exactly this kind of reason— it allows devs to confidently reach for code that other smart people have really agonized over and which definitely covers the corner cases, similar to other common utilities such as sort methods.
One example: I display available memory in my status bar, which expects strings to be a constant width. If it displayed 1000kb, it would cause alignment issues and annoy the heck out of me
Yeah, copying an incorrect answer from SO thousands of times is much better!
(The subject at hand isn't whether libraries are good or not, it's whether copying something off the internet is. In the post, it turns out it isn't. If it was a library, the author could have fixed and updated the library, and the issue would be fixed for everyone that uses it. left-pad isn't an issue with libraries per se, it's an issue with library management)
I'm hoping the changes will improve latency. I really liked neko, and wanted to use it for hosting watching parties with friends. For testing, I ran neko on a beefy EC2 instance to totally eliminate the chance that my CPU was making it run slowly, but it was still unacceptably laggy for streaming videos.
> Do you have any information about the environment in which a card was used?
That would be even more true for cards owned by non-miners; most miners will operate at a large enough scale to use some best practices, which definitely isn't true about most people who buy GPUs for personal use.
