ChaoticNeutralCzech

Now seriously, the videos recommended by the algorithm to someone aren’t theirs. People use these posessive pronouns way too often in English and it drives me mad.

NewPipe rewrite release when? It's been 9 months!

Strange, months-old versions work fine for me, and the update is not too difficult either. On an ARM64 device, you open RVX Manager, check for the recommended YouTube version, download it from APKMirror, optionally check its hash, pick it in RVX Manager, and patch it (takes 2-5 minutes). You can also press the 💾 icon to save the trusted APK you made so you can share it to other devices, including ARMv7 ones.

where are my videos

Tap “You” → “Your videos”

I know, I’m an electrical hobbyist. Most 10mΩ resistors (no space because it's an adjective) are SMD because leads would introduce significant resistance that changes when bending. Unless the wire is the shunt, of course. They have large pads and are thick to accommodate the current and power dissipation because their main use is measuring current in the order of A.

Meanwhile, 10MΩ ones are usually THT and normal size, the occasional ones rated for multiple kilovolts or spikes of even higher voltage are longer to prevent arcing.

Makes sense. I don't think latency is a great issue when transferring large files, I would be more concerned about packet drop. (Unless latency is part of the reason the tracker thinks I'm too slow to bother requesting data from, which would explain why American-based trackers barely let me seed but local ones work great.) The overhead of TCP torrenting is about 3-4 % for me, and even if an IPv6 tunnel increases that to say 25 %, I will be able to use 80 % of my upload bandwidth for seeding, assuming IPv6 allows me to reach enough peers to request 1.6 Mb/s from me, which would be much higher than the current <1 %. My logic was that I could reach people that don't have a publically reachable IPv4 port but an IPv6 one (because of IPv4 exhaustion of course), but now I understand that this is way less of an impact than I thought.

When inconsequential, capitalization gets messed up all the time, and the mistakes are overlooked: everyone understands that a weight labeled “10 KG” has a mass of 10 kg, but it's better to get used to good practice for when it does matter. Thankfully, the “M/m” mistake of 9 orders of magnitude is usually caught by humans before it gets out of hand: you wouldn't order 1 mm³ of wood instead of 1 m³. Very few quantities span 9+ orders of magnitude, for instance 10mΩ and 10MΩ resistors exist quite commonly, and you can imagine one being mistaken for the other with people copying each other's handwritten component list. However, I'd bet that the bit/byte dichotomy confuses hundreds of people every day so we better make that clear by not breaking rules.

BTW, the word is “megavolts”, not “MegaVolts” or any other capitalization, similarly “byte” is correct unless at the start of a sentence, with title case, or in German, and perhaps in words like “MByte”, which I discourage in favor of the full form or complete abbreviation.

It's supposed to say “Mbit” or “Mb”. Capital B infers bytes. Incorrect capitalization is one of the most common mistakes when using the metric system. It may be popular but it becomes a problem when 1 B = 8 b, or when 1 MJ = 10⁹ mJ. By the way, common ad-hoc abbreviations like “kbps” as opposed to “kb/s” or “PSI” instead of “lbf/in²” also grind my gears, luckily most such mistakes only occur in imperial units.

Byte is the 8x bigger one – longer word – capital B (but the word, unless shortened, is "byte", not "Byte"),
bit is the 8x smaller one – shorter word – lowercase b.
There is a roughly 0.8% difference per order of magnitude between 1024-based binary prefixes (ki=kibi, Mi=mebi, Gi=gibi, often incorrectly written as k, M, G) and 1000-based metric prefixes (k=kilo, M=mega, G=giga) but these ballpark numbers are not affected.

Anyway, do you think it's worth trying in terms of security against threats and law enforcement, or should I use a VPN on top?

Please don't say “MBit”, it makes my eyes hurt.

My internet plan tops out at 2 Mb/s upload so that wouldn't nearly fill such a public tunnel broker's bandwidth, and I would be glad for even half that, but right now I seed 500 GB of reasonably popular movie packs and the long-term average upload is a few kilobits per second, not worth spinning up the 10W HDD motor for. Yes, I expect some overhead with tunneling but not three orders of magnitude, and I need at least 100 kb/s to get a good ratio on those movie packs.

Don’t destroy it, I’m glad a perfectly working one got trashed. I recently found a small office B/W LaserJet MFP from 2014 next to an e-waste bin with no obvious damage. I was glad this was a pre-Instant-Ink model, as signing up to the service would permanently remove the otherwise legally mandated ability to use aftermarket supplies. I carried the heavy thing home and disassembled it just enough to wipe the condensation from the previous night’s rain off the scanner glass. I factory-reset it and it turned on without errors but printed with terrible streaks despite claiming 80% toner left. Turning the cartridge’s drum manually still produced the streaks, so I bought a different one for 10 % of HP’s price (twice as cheap ones were available too from less reputable brands), and it works perfectly. There is only one warning per aftermarket cartridge installation, the rest can be disabled. Unfortunately, it always advertises HP paper when it runs out but I will never be giving money to these scumbags. I use it via Ethernet (it has no Wi-Fi) and disabled its internet access with a firewall rule. My roommates do a lot of printing on our Epson inkjet EcoTank and this one is way faster and more capable (but B/W).

From Murderous Maths: Savage Shapes written by Kjartan Poskitt and illustrated by Philip Reeve