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.
You will when people sell mods for phones, such as a replacement back wth easy access.
Or when phone manufacturers realise they may as well do so, at least on some models, because why not. And yes, the battery compartment can be waterproof with a rubber seal... but even so? Many would prefer battery swap to full waterproof, if that was the cost.
The trade-off between having the field-swappability feature and going the lean way (it's not just cheaper, also smaller, lighter, less to go wrong) shifts though: when regulation forces companies to go 20% of the way towards field swappability, more will take the bet that there might be a niche worth serving at the 100% mark.
I still would not expect this to happen for mainstream phones, but other devices? There will more field swappability with the regulation that enforces layman replaceability then without.
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.
With IPv6 there is even an extension to go to 4 GB packets (extremely rare to actually be implemented though), which you can send in less than 100 ms with an 800G NIC!
Heh. Anyone remember the ping of death[0]? A lot (most?) of computers on the early internet didn't properly handle large packets, _especially_ from ICMP pings. Once upon a time, you could send a single ping w/ a packet size of 65536 and crash the remote.
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'.
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.