You can assume I'm Dan-ish. But let me tell you something...In the old world we all are used to, I have been called Turkish several times...In the coming world order, I'm/will be someone important.
Mate, please be more constructive, especially since "FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software."
UPDATE: I see you did so independently just moments after I submitted the above. Thanks for doing so
Yes, the amount of CO2 each person produces is noticable, especially in such a small room.
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've never been sure how to reconcile this with advice about insulation.
It's currently really cold where I live, and I am trying to limit outside air coming in as much as possible. This then leads to the air having uncomfortably high levels of CO2, as confirmed using an air quality sensor.
Agree. I got a CO2 monitor for my office a few ago and it was a real eye-opener.
It has made me notice "stuffy" air more keenly and helps me avoid it. If I'm stuck in a physical meeting room at work I take lots of walks and breaks. etc.
I haven't tried the CO2 sensor in the bedroom. We like to sleep with fans on and the bedroom door open, which I suspect helps somewhat (depending on how drafty one's house is overall) although is obviously not as effective as having a window open.
It's been many months since I tried, but I think you have to redo thateach time you restart Firefox, i.e. contrary to Chrome, you cannot make it persistent.
The asymmetry stems from the days where we connected through the phone lines, which was not designed for data. There it was possible to have a higher bandwidth out from the phone switches than in. That is, dial-up modems and DSL modems could have a much higher download speed than upload.
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.
The asymmetry stems from ISDN. Bonding pairs, twin lines, etc etc. that bled over into the dialup era and bled over still into the cable internet era and has even bled over into the satellite era.
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.
I think this was well prioritized; they struggled with the issue at times, found a temporary workaround, but when that workaround stöd being efficient and the bug hit them everyday, they decided to track down the source. Then they reported upstream, it was reproduced, and someone patched it, and rolled out new, fixed kernels.
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.
[Author here] Your comment resonates with me. Indeed, we had been working around the issue for a number of years before we decided to tackle it head-on and even then we set a deadline for debugging and had a fallback plan as well: if we didn't manage to figure something out in a couple of days, we would switch transports or ditch rsync altogether.
In the end I believe we struck a good balance between time spent and result achieved: we gathered enough information for someone more familiar with the code to identify and fix the root cause without the need for a reproducer. We could have spent more time trying to patch it ourselves (and to be honest I would probably have gone down that route 10 years ago), but it would be higher risk in terms of both, time invested and patch quality.
Finally, I'm always encouraging our teams to contribute upstream whenever possible, for three reasons:
a) minimizing the delta vs upstream pays off the moment you upgrade without having to rebase a bunch of local patches
b) doing a good write-up and getting feedback on a fix/patch/PR from people who are more familiar with the code will help you understand the problem at hand better (and usually makes you a better engineer)
c) everyone gets to benefit from it, the same way we benefit from patches submitted by others
> ... can submit patches to address accessibility later.
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."
There are working groups under the R Consortium umbrella that work on FDA-related tasks with a focus on R [0]. Folks from the pharma industry and FDA are involved.
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]
(I'm Swedish, if that helps the explanation)