And the fashion, oh wow, such an aesthetic.

Trashing!

I don’t know about videos but having a look at the OSI model is a good way to start. It covers the abstract framework for packetizing data including things like the distinction between hardware and software, envelope, encryption, application layer stuff, the whole shebang. The cool thing is by going hardware, network, application you can see where responsibility are and it helps you understand where things can go wrong.

If you are interested there are plenty of CCNA style courses available on the internet, licit and otherwise, and they go into more depth, and the same applies to RHCE/RHCSA material. The training for certifications like that covers what you want to know but also puts it in context, and again licit and otherwise sources are available.

Do you want a grilled human? Because that’s how you get grilled human.

In Australia we have a robust and fast paper voting system administered by the Australian Electoral Commission. We get most results in the evening of election day with only really close races being a couple of days out. There is solid chain of custody on paper ballots and having been used for over a century we have all the kinks worked out.

The USA has about 330 million people, we have about 25 million. The voting population of each is smaller, but it is a much larger percetage of our population due to compulsory voting. If we can do it with less than 10% of the population it could be done there with the same ratio no worries, just assume out country was a state and you can see it can work.

Paper is safe and secure. It is well understood and all the hack and hijinks have been worked out. If you ask experts in IT if they think voting should be dine electronically they answer hell no without much debate.

Damn autocorrect, yes, absolutely, thanks for that

Yeah, they mean in terms of the limitations if silicone, specifically the gate sizes and other properties. If the whole chip is silicone then you are bound by those limitations, but by changing to carbon things can be smaller and more efficient, allowing better computation with less waste heat.

It looks like it is downsampling the video or streaming after converting to another codec. Some codecs are fine for decoding on the server but the app may not support them so the server converts them. Some files are of higher quality than what the server is configured to deliver so it downsamples to stream it.

Check the configuration and look for anything to do with codecs, hardware decoding, streaming quality, and so on. It may also be on the app, so if you can access a different interface then test that to narrow down the issue.

I have my headphones in literally right now. I use my phone as my primary media system, so video sources like YouTube and Nebula and audio like music and podcasts. I listen with wired headphones for any time I am not physically very involved as they are higher quality and provide a much more enjoyable listening experience, but I will switch to Bluetooth headphones when being more physically active.

That said, I am a very high consumer of audio. I currently have 129 podcasts I am subscribed to (some no longer run, but most are weekly to monthly), along with a whole lot of audiobooks. I am currently at well over 2200 hours played in my podcast app this year and that excludes all the audiobooks and videos.

Something I have found is missing from both of these suggestions as well as every podcast app on device is transcoding to speed up so it is not sped up on the fly. For a lot of phones and other devices the task of playing back at 2x speed is enough to demand a higher power state than what is required to play a sped up file. For efficiency doing a single pass of speeding up the audio then playing back at that speed would use less power during the playback phase, allowing you to download and speed up all of your podcasts at home while on charge then listen for long periods without completely killing the battery. I have checked with a few if the open source devs and this is not a feature they see utility for so nobody intends to make it.