Notices by ocdtrekkie (ocdtrekkie@mastodon.social)

@Gargron It baffles us here too. We're sorry.

@nixCraft It's complicated because this is... not a scenario you'd generally plan for. There's a good chance you wanted to protect your disaster recovery plan and put CrowdStrike on your backup infrastructure!

@nixCraft To be clear, Grammarly is a keylogger. There is no setting to make it not one. It should be removed, full stop.

@foone This seems like a very convoluted way to break Windows Recall.

@arstechnica Aaaaand NOW we know why Google is so upset. Samsung is going to be asking for a big pay raise next year.

@itsfoss On one hand, great! Though this is another reminder just how far behind open source can lag behind sometimes. Bitlocker was like... 2009 or something?

@Gargron I mean, I'll be getting one just because my 11's screen is starting to fail and the battery is starting to wear down pretty badly.

Nobody needs a phone anymore before their old phone starts failing.

@Gargron Corporations trying to be funny either goes really well, or really, really badly.

@nixCraft I will go back to a 2G Nokia before I'd go back to an Android ever again. Windows 10 Mobile was still my favorite phone experience.

I don't really want to buy heavily into the iPhone ecosystem because of the proprietary nonsense, but it's incredible how much Stockholm Syndrome people have with Google and Android. It's absolutely terrible.

@oskardudycz @smallcircles @dr2chase @Martindotnet The problem is that "opt-in won't work" is an admission that opt-out telemetry is abusive and unethical. If you can't convince people to enable it, it can be understood as something people do not want. Unwanted behavior installed on people's machines is malware.

@alcinnz That all makes sense. I just an generally in favor of relatively standardized CoCs, such that I can assume they're reasonable at a glance. It looks like Django got theirs from someone else too, mind you.

@alcinnz Have you considered the Contributor Covenant? https://www.contributor-covenant.org/

@rysiek @alcinnz @slightlyoff @chriscoyier Specifically, much of the promotional content about "dealing with" the Apple browser monopoly on iOS comes from Googlers (and ex-Googlers working on Chromium at Microsoft).

You know, the sort of people deathly worried about "competition" while working on something that already has a 70% market share that they're really trying to grow.

@rysiek @alcinnz @slightlyoff @chriscoyier I was not referring to you.

@rysiek @alcinnz @slightlyoff @chriscoyier I mean, my point is that almost all promotion for enforcement against Apple before Google is written by one of the people that was in this running conversation you entered, who has a major conflict of interest. Independent groups like Open Web Advocacy tend to almost solely hinge on his position as a citation.

@rysiek @alcinnz @slightlyoff @chriscoyier It wasn't directed at you, it wasn't intended to group you, but I think the position that iOS on Safari is a bigger problem than Chrome being already literally everywhere else is really strange and confusing in the light of all of the surrounding information.

@rysiek @alcinnz @slightlyoff @chriscoyier I'm not sure why you're being so adversarial. You entered this conversation claiming that my position (that we deal with Google's abuses before Apple's) was upside-down. Which implies you think we should deal with Apple's abuses prior to Google's, despite the latter being worse.

@rysiek @alcinnz @slightlyoff @chriscoyier No guilt-by-association attempt was directed at you, I apologize if I made that unclear. Cory cites OWA directly as a source, which I find very problematic, as they have a juvenile understanding of antitrust.

The problem is when Apple loses their browser ban, the web will end very quickly as an open thing. It will hit like a truck, and we'll all be wondering what happened after.

@rysiek @alcinnz @slightlyoff @chriscoyier I agree that depending on Apple is a truly dire situation, but Google has already systematically dismantled most of the web's defenses.

@slightlyoff @alcinnz @chriscoyier I've already explained what's different: There are already numerous vendors that demand clients use Chrome. However, they have to meet web standards because they want to support iOS (whether through Chrome or not). Once Chrome on iOS is Chromium, the need to write code that supports web standards is gone.