389 karma · joined March 5, 2011
GitHub: https://github.com/pdmccormick
[ my public key: https://keybase.io/pdmccormick; my proof: https://keybase.io/pdmccormick/sigs/OrKXSd2zp2Th8eFGRrxu1hQKb9wH0tnQel0Yd089mU0 ]
Message from the administration of Northeastern Health System - Sequoyah:
Although Dr. Jason McElyea is not an employee of NHS Sequoyah, he is affiliated with a medical staffing group that provides coverage for our emergency room.
With that said, Dr. McElyea has not worked at our Sallisaw location in over 2 months.
NHS Sequoyah has not treated any patients due to complications related to taking ivermectin. This includes not treating any patients for ivermectin overdose.
All patients who have visited our emergency room have received medical attention as appropriate. Our hospital has not had to turn away any patients seeking emergency care.
We want to reassure our community that our staff is working hard to provide quality healthcare to all patients. We appreciate the opportunity to clarify this issue and as always, we value our community’s support.
That being said, I am somewhat disappointed that the general exploration of that solution space, and the creative use of those kernel features, seems to have ended as systemd matured, expanded its' scope and saw widespread adoption. I also think that the extent of systemd's authoritative dominance over the ecosystem has had a negative impact on user freedom in the broader world of open source. The fact that Snap has actively made a policy choice to _not_ give users the ability to completely disable automatic updates[0] and instead force at least weekly updates is I believe an example of the kind of "we know better than you" mentality that systemd has helped to foster and normalize.
I'd encourage everyone to sometime try booting a Linux machine with boot argument `init=/bin/sh` and see what it actually takes to get a system up to a running state with working networking.
[0] https://forum.snapcraft.io/t/disabling-automatic-refresh-for...
X509v3 Subject Alternative Name:
DNS:cloudflare-dns.com, DNS:*.cloudflare-dns.com, DNS:one.one.one.one, IP Address:1.1.1.1, IP Address:1.0.0.1, IP Address:162.159.36.1, IP Address:162.159.46.1, IP Address:2606:4700:4700:0:0:0:0:1111, IP Address:2606:4700:4700:0:0:0:0:1001, IP Address:2606:4700:4700:0:0:0:0:64, IP Address:2606:4700:4700:0:0:0:0:6400
You can inspect the certificate yourself with: openssl s_client -showcerts -connect 1.1.1.1:443 < /dev/null | openssl x509 -text -noout
Too bad Let's Encrypt will not issue certificates for IP's at this time.My favourite use for this feature is via `qemu-user-static`, which allows you to transparently "run" executables compiled for other architectures thanks to QEMU emulation. Very handy for embedded systems development.
While working, I’m freely taking advantage of Git’s capabilities on a personal level, producing many sometimes messy WIP (work in progress) commits, trying things on short lived branches, reverting changes, and so forth, but afterwards I am able to copy edit the results to produce a sequence of finalized commits that form a coherent narrative that reads like how I would describe my work to a colleague or manager.
To me, interactive rebasing has been the difference between “my team uses Git” and “I first and foremost use Git for myself, and then also use it to share the results with my team”.
There is a full duplex version of DOCSIS, but its adoption faces some challenges due to how operators have to re-architect their physical networks to support it.
There is also currently a push to extend the downstream spectrum up to higher frequencies, enabling both more downstream bandwidth and also the ability to move the upstream split higher, therefore increasing upstream bandwidth.
(Disclaimer: I work with a client who develops products in this space.)
Yes, 2 + 2 does not equal 5, but we need more people who can explain and think about _why_, and not simply repeat "just because". If someone cannot debunk a misconception as rudimentary as that, how can we expect their arguments against a flat earth theory to be sound and persuasive?
Fast compilation speed, easy integration with C, and the "one large static binary" are probably my favourite features, although I do wish those binary sizes weren't quite so large...
Enjoy!
To me, the beauty of the story is that, while we as viewers do not know what has transpired in the universe between 1973 and present, neither does Wolverine. Further, since he stills ends up at the School with his friends alive in the present day, we know that a lot of character development has necessarily happened, because we saw analogous stories in the earlier movies from the now lost timeline. So while the events of the previous movies are now no longer canonical history, they are as real to Logan as they were to us, and their emotional impact still affected Logan's life in a very real way. Meanwhile, going forward the script writers are no longer slaves to continuity, which, after the third film blew up everything, greatly restricted what they could do with the main cast of characters in the present day setting.
In my opinion, so many "time reset" plots (think Star Trek Voyager's Year of Hell) leave the viewer empty because they truly have no lasting consequence on the character's we love. SF Debris (http://blip.tv/sf-debris-opinionated-reviews/voy-year-of-hel...) made the incredible suggestion that, in that Star Trek story, imagine what if, due to some kind of quantum chronometric mumbo jumbo, one of the crew members (say, Harry Kim!) had survived the big reset with their memories and experiences of the year intact. But instead, apart from some shallow insights into the characters in a "what if" scenario, it was as though it never happened.
Historically speaking, his act of open sourcing those codebases and the chronicle of cutting edge graphics/gaming development that they represent is a significant record of and insight into one of our generations leading minds. His work ethic and dedication is pretty phenomenal, he is a big personal inspiration.