I don't recall 2s latency, but do remember 0.25-0.3s latency one way for transatlantic phone calls in the 90s, which happens when the call got related over geostationary satellites rather than over Atlantic cables. It was basically a 0.5-0.6s roundtrip delay enough to cause you to talk over each other.
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.
Agree - I read this as it will be easy to replace the battery when it reaches its end of life and no longer can hold my charge. It will still take time to replace it, but that's okay since it'll only be done once every few years. It's not meant to re-introduce swappable battery packs, so you won't be able to carry spares on long trips etc.
The copyright holder can set whatever license they want, including writing their own.
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.
It's humbling to know that the RAM of computers like ZX Spectrum and Commodore 64 would fit in a single IP packet. It took minutes to load that "paket" from cassette tape.
Another way to donate is to proof read documentation and report on typos, spelling errors, etc. Some projects have documentation in multiple languages - helping out in a language you know is another excellent way to contribute.
Many projects have great communities, making it all fun and engaging.
WISH: Don't pad the hours with zero when using the 12-hour time format, e.g. '7:15:03 AM' instead of '07:15:03 AM'. The padding with zero is used in the 24-hour format, e.g. '07:15:03'.
I remember connecting a VHS video camera directly to a cathode-ray tube (CRT) teve to produce funky patterns back in the 80's.
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.
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.
FWIW, the 'AVX' CPU feature is part of the x86-64-v3 level of the x86-64 microarchitecture standard [0].
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.
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.
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)
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.