m01

> Participants wore an Apple Watch on one wrist, and a comparative wrist-based device on the other, while using a Polar H10 ECG based chest strap as reference. Wrist assignment was randomized such that Apple Watch was worn on the dominant hand approximately 50% of the time. Wrist-based devices studied included Apple Watch Series 12, Garmin Forerunner 970, Google Pixel Watch 4, Huawei Watch 5, Samsung Galaxy Watch 8, and WHOOP 5. Oura Ring 5 was also worn on an index finger, per the manufacturer's stated best practices3

It's been a long time since I last used Mp3tag, so I tried the latest Mp3tag in WINE (seems to work nicely) for comparison. I think the basic operations (editing tags) actually do work similarly: in both you select file(s), edit the tag you want to in the GUI and changes get applied to any selected file(s) when you press save.

Renaming filenames based on tags also works according to that principle in kid3, you select the files you want to change (rename) and then use the `Format (arrow pointing from tag fields to filename field)` to specify what the filename pattern should look like and then use the `Tag 1` or `Tag 2` button to fill the placeholders from the (e.g.) ID3v1/ID3v2 tag, and click save to apply the changes.

In Mp3tag you'd also highlight the files, but unlike other tag editing operations you use the `convert->tag to filename` menu item/button, which pops up a wizard asking for the pattern and confirmation.

I'm guessing coming from Mp3tag you tried to use kid3's `Tools->Apply filename format` option, which I believe ensures the filename doesn't include special characters by doing string replacements (these are configured in the settings under `Files->Filname format`). I was wondering if that was perhaps confusingly named, so I had a look in Mp3tag to see what this functionality was called there, but I couldn't find it. I'm sure it's possible somehow, but it probably involves scripting [1].

I noticed that Mp3tag seems to be able to automatically fetch album art whereas in kid3 you need to get the image yourself. I suspect more advanced functionality (scripting etc) will work differently in the two tools.

> Opting out of vehicle data: Connectivity and performance is a core part of all Tesla vehicles and why some customers choose Tesla, allowing for advanced features and an enhanced driving experience. By default, Tesla provides this seamless experience while protecting your privacy. However, if you no longer wish for us to collect vehicle data or any other data from your Tesla vehicle, please contact us to deactivate connectivity. Please note, certain advanced features such as over-the-air updates, remote services, and interactivity with mobile applications and in-car features such as location search, Internet radio, voice commands, and web browser functionality rely on such connectivity. If you choose to opt out of vehicle data collection (with the exception of in-car Data Sharing preferences), we will not be able to know or notify you of issues applicable to your vehicle in real time. This may result in your vehicle suffering from reduced functionality, serious damage, or inoperability.

I don't know if anyone has tried this.

There are other EVs where it's easier, but it's not something typically featured in the main marketing material.

Regarding eCall (emergency) functionality, "Under EU rules you have the right to use a third party service (TPS) eCall system in addition to the standard 112-based one" and "Any TPS eCall system must: [...] allow the owner of the vehicle to choose between the 112-based eCall and the TPS service" - which also means manufacturers can't force you to use "their" TPS that probably has different privacy trade-offs.

If you would like your IPv6 addresses to be more human-friendly, you could use DHCPv6 (in addition to/instead of SLAAC) and end up with addresses like 2001:db8:3c7:4f80::123. Sure, it's 5 groups of e.g. 3-4 hex digits rather than 4 groups of up to 3 digits, but I think it's much easier than your example. You might set your router to use <prefix>::1 and/or fe80::1 (see OpenWRT's ipv6 suffix/ip6ifaceid option).

DNS servers (that you might occasionally have to type into config by hand) tend to have "nice" IPv6 addresses, e.g. Quad9 apparently uses 2620:fe::fe [1].

> But I'm really not interested in maintaining public DNS for the dynamic addresses at home on my LAN.

I think dnsmasq can these days create AAAA records for local machines whose hostnames it learns via e.g. DHCP.

If you have a public server on the internet and your provider gives you a random-looking address using all 128 bits (and no /64 prefix for example) perhaps using (public) DNS is fine.

Opinions my own.