To be clear, if it he happened on and off that eliminates a bunch of potential causes. It is entirely possible this is just a loose ribbon cable or similar, though it could be a different kind of intermittent. Does it happen on an external monitor? What about a live USB? Both of those will isolate whether it is hardware or software to some degree.

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.

I did a whole stack of servers using SNMP based monitoring years ago and it was amazing. I could see loads, memory stats, NIC utilisation, disk space, and all sorts of other things. I tried Cacti and Icinga and settled on the latter but they are all fairly similar. Once you are generating the data you van do whatever you like with it, so monitoring load attributable to which actual executable is definitely manageable. It is also handy for getting notifications for something being down, losing stability, or just being out if whack.

I have tried both and a bunch of others with a laptop with nVidia and Intel and have had a range of experiences.

Anything Ubuntu based worked out of the box but any significant deviation from the exact current standard made things less stable. Changing WM/DE was not really possible and troubleshooting was opaque. Snap was also a nightmare of broken packages and bad update processes.

Manjaro looked really nice and had that lovely Arch flavour, but it is not really Arch, more Arch adjacent. Lots of things work similarly but lots of things break in bad ways. They have had numerous issues with security, bad updates, and general poor practice.

Pop is cool, I like it, but just not a good fit for me. Cosmic is a great environment but I like to tinker too much and while the team is great and do good work it is just not the same kind of defaults I like.

EndeavourOS is my current pick. It is Arch with sane defaults. It comes prebuilt with a DE configured, backups using BTRFS snapshots, a handy updater and package management config, some cool apps built in, and it is very performant. The guides for hardware video acceleration worked first time for me which has never happened before, normally that is a major pain and takes a few days to get sorted on a fresh install. Graphics performance is awesome, same with built in OOM protection. That said, make sure you have enough RAM. I had 8gb in my laptop and ended upgrading to 32gb after a number of failed builds and messing around with swap to get things to finish. If you have less than 16gb RAM I would recommend upgrading.

Whatever you choose, I would recommend trying a few things before settling down. The right fit is right for today and may change, so try things again in the future if you feel uncomfortable. Also do what works for you, not for anyone else. If you don’t like Arch you are not obligated to use it, same with Ubuntu, Debian, Fedora, etc. Keep the fun of it and play around, maybe just boot up a few live environments and see if something tickles you. I hear good things about Hannah Montana Linux.

Man, it looks like AI art the spelling is so bad. Impressive.

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.