Your first link, straight from the introduction:
"Our study was not designed to evaluate the overall harm-benefit of vaccination programs so far. To put our safety results in context, we conducted a simple comparison of harms with benefits to illustrate the need for formal harm-benefit analyses of the vaccines that are stratified according to risk of serious COVID-19 outcomes. Our analysis is restricted to the randomized trial data, and does not consider data on post-authorization vaccination program impact. It does however show the need for public release of participant level trial datasets."
If it wasn't designed to evaluate the harm benefit of vaccination, why are you portraying it as such?
With an ansible playbook and all my services running through docker, it's trivial to set everything up again within the hour with minimal effort compared to years ago when I did services purely through systemctl. In the future I'd like to build a DIY PiKVM and have ansible do the entire installation of the os too, but that's not really necessary for my home server so it's on the back burner.
I used to use ansible and salt but I realized that all configurations are in the persistent files so there is nothing to configure.
Now, I run services and not elastic containers - in the sense that once I have Syncthing or whatever set up, it stays that way. i do not need to pop up containers and configure them manually.
No, we learned that they were approved at roughly the same rate as other search court orders. Investigators aren't going to spend the time making an application for a court order unless it has a very high chance of being granted.
Me too. I was a long time TST user but I found I am more productive if I use stashes instead, pin the ones I use daily, and try to only keep what needs to be open in a native tab.
+1 for prowlarr. Used to run jackett but I much prefer the automatic updating of *rr services when I change my indexer settings in prowlarr.
Currently running prowlarr with sonarr, radarr, lidarr, bazarr (for subtitle fetching) all from a single docker-compose file, no complaints.
>There is nothing great about abortion. And ease and normalization of abortion for convenience has contributed to way to many over the past fifty years.
We've been doing abortions for millennia, only in the past century did we start doing safe ones. I'd be less pissed about this ruling if those in support of it would fund neonatal care and social welfare systems to support a baby that may come into this world with a mother underprepared to care for it but typically the people against right to choose don't actually care about the babies once they're born.
Foobar2k and Lidarr is where it's at. I went full circle back to sailing the seven seas because streaming services got so bloated and user-friendly in my opinion.
It's basically just a more sensitive radar detector. Instead of picking up the main frequencies radar guns use, it picks up the harmonics emitted by the oscillating crystal inside the radar detectors. All radar detectors leak on harmonic frequencies of the frequency they pick up on, it's just a matter of how much. Those cheap Walmart radar detectors leak so badly they detect each other. Pricier ones are more sophisticated in how they shield.
Could one build an SDR version of a radar detector that doesn't have a detectable oscillator? (Or, if it does, it's oscillating at a much higher frequency?)
I'm no RF guy, so I'm clueless on this stuff. But my understanding is that SDRs aren't radio receivers in the traditional sense. That's the whole "SD" part of it, the device scoops up everything and FFTs it or something.
But they are suffering from the chip shortage.
I was interested in using it as an X-band and K-band capable SDR receiver, which is a supported use case according to their media.
But we'll see when it ships.
It would be way cheaper to design the radar detector to have better RF isolation than to go towards an SDR solution.
A modern radar gun operates in the Ka-band, Google says between 33.4 and 36 GHz. Assuming 12 bit samples, your proposed solution needs to process a minimum 3.9 gigabits per second, or ~500 megabytes per second. To do this work in software would require a workstation.
Not to mention I'm not even sure if you can operate most ADCs above the 1st Nyquist zone like would be needed here.
> To do this work in software would require a workstation.
These days hardware capable of that throughput can be had for less than $500 and draws less than 50W. 3.9 gigabits really isn't all that much by modern standards.
If it wasn't designed to evaluate the harm benefit of vaccination, why are you portraying it as such?