If you're not looking to question your views, then ignore people like me who do. Though as a general rule of thumb, not questioning your own views may not be the best strategy in life but you do you.
It's fine to as that sort of question; I wouldn't say it doesn't "belong in this community". That doesn't mean it makes sense to care about this which is what I wanted to point out.
That argument ignores that you need an account to upload pictures in most places (including here); you're already identified.
Ignoring that, while it is technically true that the Android version adds a data point and therefore identifying bits of information, you'd still be one of 10^5 - 10^6 people in the same time zone with the same device/version combo unless you're using some extremely uncommon device or are in an extremely unpopulated time zone. Compared to user agent and IP address, this is extremely little information and I'd argue quite useless without. If you need such strongly identifying data to even make any use of this, I don't think it's worth worrying about.
Besides, if you control a forum or other site that allows picture uploads and wanted to identify a user, there are so much better methods than any of this.
You linked FUD.
If you have the Mossad targetting you, that's an extreme edge-case which has no place in an argument about online privacy.
Not sure it's positive; given the US' asinine privacy laws, I don't see this going anywhere.
The software version doesn’t just say “Android 14” either. It looks very specific.
Yeah, it's likely a rather precise Android version.
So what? What does the Android version you use reveal about you? What part of your threat model does it violate?
Here, you can have the exact version of my phone: lineage_FP4-userdebug 13 TQ3A.230901.001 2023111915 test-keys. Can you identify me now?
(In my case, you theoretically actually could because my version is unique because I homebrew my Android but if you didn't know that, it'd look like any other FP4 with !lineageos@lemmy.ml on it which is why I'm not at all worried.)
No matter how you look at it, this is not an acceptable way for a device to behave, with no way to change it in settings.
Adding useful metadata that reveals no actual data about the user is a great feature and not worth adding a setting for; especially not in the UI.
I didn't know about this before but I'll look out for that whenever sends a bug report of a mobile app with screenshot as it might include the device and Android version used which is super useful info to have when troubleshooting.
You've highlighted it pretty well. But you're wrong about one thing.
Stable means the packages' interfaces remain stable. I mean that term in a very broad sense; a GUI layout would be included in my definition of an interface here.
The only feasible way of achieving that goal is to freeze the versions of the software and abstain from updating it. This creates a lot of work because newsflash: The world around you is not stable (not at all). Some parts must be updated because of changes in the world around you. The most critical here is security patches. Stable distros do backport those but usually only bother porting "important" security patches because it's so much effort.
Another aspect of this is that you usually can't introduce support for these without risking breaking older interfaces, so stable distros simply don't receive new features.
Windows 95 is one of the most stable operating systems in the world but there's a reason you're not using that (besides the security issues): At some point, you do need newer versions of interfaces to, well, interface with the world. There's newer versions of software with additional features, new communications standards and newer hardware platforms that you might want/need.
As an example: Even if you backported and patched all security issues, Firefox from 10 years ago would be quite useless today as it doesn't implement many of the standard interfaces that the modern web requires.
What you are wrong about though is that stable means no breakage or that things "run smoothly". That's not the case; stable only means that it's the same sources of breakage and same level of roughness. No new sources of breakage are introduced by the distro but the existing ones remain.
Stable distros do try and fix some bugs but what is and isn't a bug sometimes isn't easily determined as one man's bug is another man's feature. If things weren't running smoothly before, stable distros will ensure that they will run similarly roughly tomorrow but not any worse.
Well, for parts that the distro can control that is. Things outside the distro's control will inevitably break. Tools made for interfacing with 3rd party services will break when those 3rd party services inevitably change their interface; regardless of how stable the distro is (or rather precisely because of how stable the distro is).
Stable interfaces and no local regressions are what characterises stable distros. Not "no breakage", "system stability" or whatever; those qualities are independent of stable vs. fresh distros and a lot more nuanced.
Is this all the metadata it adds?
Because the information you've shown here is not at all sensitive. It's just the timestamp, Android version and time zone.
I think what does and does not belong on a bicycle path inside a city should depend on speed, size and weight. Some rules of thumb I just came up with; all measured in human sizes:
- At most as fast as a sporty person on a regular bike
- At the least as fast as your average grandma on a regular bike
- No longer than two humans piggy-backed are tall
- No wider than 2 humans
- At most as heavy as 2 humans
Scooter, longboard, skateboard, inline skates, boosted board, whatever? Sure, come on in. We're about the same speed, size and weight, so we can intermingle just fine.
Big fat cargo "bicycle" with a huge-ass storage container on the back? You belong on the road.
If the motorcycle in question is lightweight, small and not very fast, I wouldn't mind it in the bike lane though.
The style you're suggesting is a bit too heavy (surprisingly just 223 kg but still too much) and obviously way too fast.
If it was lighter and had a 20-30 km/h speed limit though, I probably wouldn't mind too much. It wouldn't be much different from a cargo bike and those have proven to work just fine in bicycle paths.
That tool does not claim to support custom resolutions in any way.
This is not true. As soon as the key is wiped from the TPM-like thingy, any data left on the flash is unrecoverable.