HenrikB
It only happened when there were too many callers at the same time. The solution was often to redial and hoping you ended up with a non-satellite call.
In this case, I'd interpret it as they made up a new licence based on MIT, but their addendum makes it non-MIT, but something else. I agree with what others said; this "new" license has internal conflicts.
There are also public and proprietary "aviation obstacle" databases across the world.
Many projects have great communities, making it all fun and engaging.
https://en.m.wikipedia.org/wiki/Freedom_of_Information_Act_(...
You did it in a pitch dark room, aimed the camera towards the teve, and have someone briefly light a lighter in between. That generated a visual feedback loop.
By rotating the camera upside down, the feedback loop would introduce systematic effects, because the camera's vertical scan is now opposite to the teve's swipe. It would create random, constantly changing, colorful, spiraling patterns.
You could move your hands in front to adjust the patterns and control the brightness that could increase due to the feedback loop.
Stunning, cool, and fun.
I read a long time ago that it's quite common, like 1 in 7 people got it. Some people don't even know they have it. I always had it as far as I can recall, but it wasn't until my mid 20s, when I stumbled upon a picture, that I reflected on it and the fact that not everyone sees number forms.
There are chips produced in 2015 that are only supporting x86-64-v2 [0]. Also, according to [1], "The new server-class CPUs released in 2020 [2] do not implement the AVX instruction set."
FWIW2, RedHat Enterprise Linux 9 (RHEL9) requires x86-64-v2 or newer [1]. So, as a reference, they decided to not yet require support for AVX.
[0] https://en.wikipedia.org/wiki/X86-64#Microarchitecture_level...
[1] https://developers.redhat.com/blog/2021/01/05/building-red-h...
[2] https://www.intel.com/content/www/us/en/products/details/pro...
Yes, it looks like traveling outbound from some major hubs is more expensive than from other places. A round trip SFO-XYZ two week ticket can be substantially more expensive than XYZ-SFO round trip for the same period.
Note that depending on when you travel and for how long, a SFO-XYZ-SFO ticket might be more expensive also because it is a shorter ticket (1 month or 3 month ticket) and it hits a high season period ("tourist season"), whereas the XYZ-SFO-XYZ is a long-term ticket (12 months) that avoids (most of) the high season.
I certainly joined GDrive believing it is designed as a cloud drive where I put whatever I'd like.
(I'm Swedish, if that helps the explanation)
UPDATE: I see you did so independently just moments after I submitted the above. Thanks for doing so
If possible, keeping a bedroom window a bit open makes a noticable difference. Avoid closing bedroom door too.
Similarly, if you work from home, make sure to create a draft once in a while.
We got an Aranet4 CO2/humidity/temperature sensor mostly out of curiosity two months ago. Outdoors it's ~430 ppm CO2. 500-1000 ppm indoors is considered okay (according to the defaults), 1000-1400 ppm high, and >1400 ppm bad.
It's amazing how you don't notice how it slowly creeps up to 900-1000 and beyond. Without the device I would notice, except that I'd slowly get tired. I'd probably also drink more coffee. The device helps you see what's going on and how bad it is. Creating a big draft for 5 minutes clears everything out.
Also, you can definitely see from the historical data when one goes to bed in a ~12 m2 bedroom and then an hour or so later the second person goes to bed. Same if one gets up before the other. Definitely good evidence that keeping a window open is a good thing (if you got clean air outside)
I don't know about cable, but I suspect it's the same there.
OTH, fiber-based internet often has symmetric speeds. Don't know the stats, but I suspect most fiber ISPs gives you that.
(Disclaimer: I'm one of the authors)
After falling in love with ShellCheck several years ago, with the help of another person, I made the ShellCheck REPL tool for Bash:
https://github.com/HenrikBengtsson/shellcheck-repl
It runs ShellCheck on the commands you type at the Bash prompt as soon as you hit ENTER.I found it to be an excellent way of learning about pit falls and best practices in Bash as you type, because it gives you instant feedback on possible mistakes. It won't execute the command until the ShellCheck issues are fixed, e.g. missing quotes, use of undefined variables, or incorrect array syntax.
It's designed to be flexible, e.g. you can configure ShellCheck rules to be ignored, and you can force executtion by adding two spaces at the end.
License: ISC (similar to MIT). Please help improve it by giving feedback, bug reports, feature requests, PRs, etc.
That is a perfect example of how things works and should work. They contributed to the community. I think it was a great prioritization.
I'm certain there were lots of other people hitting this bug and killing processes or rebooting to get around it. The troubleshooting and reporting done here, silently saved a lot of of other people a lot of efforts - now and in the future. I don't think they were after it to be heroes; they just shared their story, which I'm sure will encourage others to maybe do the same one day.
I'm not experienced with accessibility, but I pay attention to it whenever I can to increase my own awareness. A very common feedback when it fails (e.g. in software, online conferences, ...) is: "Accessibility must be part of the plan from early on. Trying to add it afterwards basically always fails."
One of the working groups is dedicated toward submissions: R Submissions Working Group [1]. They recently announced: "The R Consortium is happy to announce that on Nov 22nd, 2021, the R Submissions Working Group successfully submitted an R-based test submission package through the FDA eCTD gateway! The submission package has been received by the FDA staff who were able to reproduce the numerical results." [2]
[0] https://www.r-consortium.org/all-projects/isc-working-groups
[1] https://rconsortium.github.io/submissions-wg/
[2] https://www.r-consortium.org/blog/2021/12/08/successful-r-ba...
I can run 1 Gbps symmetric for ~48h without power by running my optical network terminal (ONT) and a teeny travel router on battery packs. (Used this set up through several long power outages.)