"Pretty much" is doing quite a bit of work there. The feds ignoring marijuana use in states that have legalized or decriminalized it is the DoJ actively deciding not to prosecute MJ cases. They could absolutely send the FBI or whatever into a state with legalized marijuana and raid dispensaries and arrest people if they wanted to.
At this point I don't see any difference between the two. Modern religions are shaped (warped, really) by the larger organizations that control them.
Sure, the concept of "spiritual/non-scientific belief" isn't a parasite in and of itself, but even if the existing organized religions ceased to hold their sway, and people treated religion as a personal thing without centralized authorities, I still don't see an end to (for example) people trying to get their religious beliefs enshrined in law. That's parasite behavior.
unless they have edited they do not say Wales and Scotland are England, they complain the trail is not contiguous, which to be fair might also be implied by the fact that Wales and Scotland are not England but I guess I could see a scenario that allowed made the trail contiguous, which would still allow you to walk the English coast, but also of course allow you to walk some other parts that are not on the coast.
You're replying to someone who is talking about a native app, but the overall issue here is about web apps. Chrome and Firefox don't request the appropriate permission (which, as things stand right now, is probably the safer choice), and there's no way for a website to signal to the browser that it wants that permission, so that the browser could prompt the user only for websites that ask for it, and persist the allow/deny response, similarly to how general location permission works via the JS location APIs.
That's not sufficient. We need a standardized attribute on the HTML form to request the permission as well. If Chrome requests the permission, great, but that's not fine-grained enough for a web browser.
Well yes, agree, but as stated Chrome didn't end up with this behavior because they did something, the Browser behaves like this because they didn't implement any logic for this permission.
A standardized attribute on an HTML-form would be difficult to define, because in this context the page just requests/receives a binary file, so a generic "strip embedded location information" decision from the user would be hard to enforce and uphold (also, by whom?).
In this case Android only knows the file-structure and EXIF because the file is requested by Chrome from a Media Library in the OS, not a file-manager.
W3C keeps thinking about this data-minimization topic repeatedly [0], so far they managed to define the principles [1], but enforcing them technically is quite hard if any kind of content can be submitted from a storage to a webpage...
You do realize that Google only cares about user privacy when it doesn't affect their own business model to do so, right? And also, like in this case, where not caring could end up creating some nasty headlines that hurt their reputation?
Meanwhile, Google probably has one of the most comprehensive databases on the planet of user behavior, gleaned from tracking their users all over the internet. Surveillance capitalism at its finest. But hey, they protect people from accidentally sending their photo geolocations to random websites, so good job Google, pat on the back for you.
Ah yes, the good old, "I don't have that particular issue, so I can use my experience to dismiss your concern".
You do realize that sometimes bugs only affect a small percentage of users, right? And even if it affects, say 40% of users, you may personally never see the issue. Does that make it not worth talking about?
And what would be the alternative that doesn’t have tradeoffs? Everytime you get into your car you have to press a button to manually pair your phone with it? Then another set of users would complain.
The same with the EXIF data being shared. Most people don’t want their location being shared with photos and there have been reports of stalkers using the information
reply