hellfire103

Bringing a whole new meaning to a sting operation.

Pure chromium is alright, but you really shouldn't lick any compound containing chromium(VI): they're highly carcinogenic.

• DAITA adds noise to your traffic, in order to prrvent AI packet analysis. However, most people don't need this, and it limits your server options as well as increasing your bandwidth usage. Leave it off unless you need it.
• Multihop routes your traffic through two Mullvad servers, in order to further obscure your IP address. Turn it on for added privacy, unless you have problems as a result.
• Local network sharing means you can still connect to devices on your home network while using Mullvad VPN. This includes things like networked printers, network attached storage, and the web interface on your router. Turn on unless you're sure you don't need it.
• API access just checks to make sure you can connect to Mullvad at all. The API is what gives you the list of servers and provides your computer with the connection info. Have a look if you're interested, but you shouldn't need to change anything.
  • If you are on a hostile network, this part of the settings also lets you enable bridges, which can help to circumvent local VPN blocks.

Almost ate the onion there.

Metro, but I've had the same problem in all the other Android music player apps I've tried.

Yeah. Trouble is, MusicBrainz Picard is set to use UTF-8 for all file formats except WAV, and this issue hasn't affected ¡Uno! or ¡Tré!.

I also couldn't find a tag to set the encoding.

This problem is present in every music player I've tried on my phone. My old iPhone, however, was fine (I was using foobar2000, btw), as are my laptops.

Even more annoyingly, track 12 (Wow! That's Loud) appears to be tagged ever so slightly differently, and in a way I can't seem to replicate, that means it appears in its own album with the correct title.

I have not yet tried reimporting the CD, as it's currently 114 km away, on the other side of the England/Scotland border.