u/jankanis

The only reason is that nobody has bothered to write a free tool that does it. The guys at DiskGenius did, but they are not sharing their code. ExFat is a relatively simple file system (as far as filesystems go) so there's no impassible hurdle why it couldn't be done, but nobody has found it important enough to write and release the code.

In 2025, there are a bunch of flags when you search for 'reader' in brave://flags. Enabling any of the 'reader mode' related flags enables a reader mode item in the brave menu. Though it only works on article-like sites. There's also a speedreader, which gets its own menu item and appears to be a separate type of reader mode, one more suited for larger screens.

My experience is similar, my 2.5" 5TB barracudas so far don't last very long. I have two barracudas of 6 years old, one is still working without any problems, the other started failing after 3 years. I then bought a new one which is now also 3 years old and also starting to give failures. I'm now looking to replace them with other drives because I don't trust them anymore. I'm using them for occasional writes and heavy reads (serving static data).

Both failures have so far been the same intermittent failure: the drive starts giving i/o errors on any attempted read or write and is completely inaccessible, but a full power cycle restores the drive back to working order. Heavy activity can then trigger the same failure again. I also noticed that regular reading from the most recently failed drive is much slower than it is supposed to be.

You can of course implement dicts with O(1) lookup in fish. Just like you can in C or in machine code, which don't have builtin associative arrays either. But you'll need to implement all the logic for hashing and collision resolution. That probably gives a lot more overhead compared to iterating over an array of key-value pairs, until you get to really huge maps.

For a determined attacker it would be easy to try all the passwords from your 2nd password manager against the 1000 or so most popular web services.

Not sure about the calculation for 4 words, but Dashlane's calculation for the 16 character password is quite wrong. If I assume all non-space printable ascii characters are used (which many password fields won't accept), that is 94 characters. Each character has log₂(94) = 6.55 bits of entropy. For 16 characters that is 105 bits. Strong enough, but no where near "between 200 and 250 bits".

As a workaround I'm now using the youtube mobile website in Brave: - No ads - Background playback (enable in Brave settings) - History and other YT features just work.

While not ideal, for me this has proven so far a better compromise than the add-laden app or RVX without history.

But calls may require a 2G/3G network on OP's phone, so this test won't work.

The storage chip is housed in the USB-A connector. The USB-C connector is smaller and doesn't have the space to house the storage chip (yet).

For anyone reading this now I'd like to point to the Fenix E-STAR flashlight which has come out. It has both a rechargeable AA battery and a squeeze crank + supercapacitor for when the battery is dead. And it is getting positive reviews on this reddit. https://www.fenixlight.com/product/detail/index.php?id=166

The Arctis Pro Wireless has Bluetooth and a proprietary 2.4GHz protocol as wireless options. Bluetooth is encrypted, lots of info to find if you google it. It appears that it uses the Avnera AV6301/AV6302 chips for the proprietary protocol, which is called VMI RF protocol (which is digital by the way). There is barely anything public on that protocol to find, but there is a leaked datasheet on the AV6302 floating around. It doesn't list the details of the RF protocol, but it does list its features (audio channel capabilities, error correction, audio error concealment, latency, etc). There's no mention of encryption or anything like it whatsoever. In such a document listing features I would expect that to be mentioned somewhere at least, so based on the lack of mention I am 95% sure the VMI RF protocol is not encrypted.

But until details on the radio protocol are published, only someone with an SDR and access to the proprietary details, or with the willingness to invest a whole lot of effort to reverse engineer the protocol, will be able to decode it. So don't use your Arctis with the 2.4GHz protocol to discus things a secret service or the mob might be interested in, but it's probably safe from other gamers trying to cheat.

For other headsets it depends on what radio protocol they use. But the Avnera chips are used by other gaming headset brands as well, and if a top tier headset like the Arctis pro is not encrypted I wouldn't bet cheaper headsets to be.