souplesse
Joined 5 years ago
Joined 5 years ago
Obviously there's a difference between defecating on the sidewalk and recklessly injuring someone with a car, so the question becomes how we define harm.
There are absolutely worthwhile discussions to be had about the ethics of dealing with abusive or greedy corporations, or about whether rent-to-own contracts are predatory.
But just because the community doesn't immediately jump to say "telcos suck so stealing your phone is a moral imperative" doesn't mean commenters are groveling at the feet of T-Mobile.
The kind of unlocking at issue in this case refers to a) unlocking phones that a customer owes a balance for or b) unblocking stolen phones (which are blacklisted by carriers to deter theft).
The paragraph you're quoting ("'Technology that detects...scope of the problem.'") is entirely commentary from Erin Earp at RAINN, and is what was added by WIRED with the edit.
And, sorry to nitpick, but "Countering CSAM is a complicated and nuanced endeavor [...]" has always been the last paragraph (both before and after the edit).
The announced opt-in feature for iCloud family accounts (Communication Safety for Messages) will scan content that is sent and received by the Messages app, and alert the associated parent or caregiver directly, without informing Apple.
The parent made no such suggestion. You seem to be conflating the purpose of HTML classes with CSS. Here's a note from the "literal entire spec"[0], which other commenters have already pointed out:
> […] authors are encouraged to use values that describe the nature of the content, rather than values that describe the desired presentation of the content.
Furthermore, the parent took great pains not to attack Tailwind, instead pointing out that the two different approaches could easily coexist.
If you'd like to use class names solely as CSS hooks, go right ahead, but citing "correct attributes" is ironic at best.
[0]: https://html.spec.whatwg.org/multipage/dom.html#global-attri...
The iOS location request prompt uses very clear language while allowing for granular access, and the granted permissions are easily reviewed in Settings.
The App Store requires data usage disclosures, which are presented about as succinctly as possible.
They could mandate that apps share absolutely no location data with any third party, but that would break all sorts of things (external mapping APIs, for example), and it’d basically be impossible to police.
Are there mitigations they could provide that I’m missing?
There’s nothing wrong with Outside sharing nice places with world, but it’s ironic that they would also publish an article decrying the very popularization that they themselves often cause.