Opt-in should be mandatory for all services and data sharing. I would start my transition to Linux today if this were opt-out, though the way Apple handles this for other services makes me believe opt-in will be temporary.

Currently, when you setup any device as new, even an offline/local user on macOS, the moment you log into iCloud it opts-almost-every-app-and-service-into iCloud, even one’s you have never used and always disabled on every device. There’s seemingly no way to prevent this behavior on any device, let alone at an account level.

Currently, even though my iPhone and language support offline (on-device) Siri, and I’ve disabled all analytics sharing options, I must still agree to Apple’s data sharing and privacy policy to use Siri. Why would I need to agree to a privacy policy if I only want to use Siri offline, locally on my device, and disable it from accessing Apple’s servers or anything external to the content on my phone? Likely because if you enable Siri, it auto-enables (opts in) for every app and service on your device. Again, no way to disable this behavior.

I understand the majority of users do not care about privacy or surveillance capitalism, but for me to trust and use a personal AI assistant baked into my devices OS, I need the ability to make it 100% offline, and fine grained network control for individual apps and processes, including all of the OS’s processes. It would not be difficult to add a toggle at login to “enable iCloud/Siri for all apps/services” or “let me choose which apps/services to use with iCloud/Siri, individually”. Apple needs stronger and clearer offline controls in all its software, period.

Even if it were just a thing, Apples implementation would be limited and inflexible, so I’d probably use an app anyway.

Lucky! I finally got my mum to use the password manager I admin, but she still reuses the same dozen passwords for everything and manually enters them in… sigh. I’ve set strong passwords and 2FA for all critical accounts, so I just let her be a moron with the rest of them.

Computers break her brain. She literally responds with questions like “it’s IN the computer?” Zoolander style. I just do most of her shit myself because it’s less painful than trying to teach her.

One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed. In comparison, one of the four pillars of the Agile Manifesto is “Working Software over Comprehensive Documentation.”

Requirements ≠ Documentation. Any project with CLEAR requirements will be most likely to succeed. The hard part is the clear requirements, and not deviating.

One Agile developer criticized the daily stand-up element, describing it to The Register as “a feast of regurgitation.”

The inability of management to conduct productive meetings is even more well-known than their inability to conduct a decent hiring process, and we all know how broken that is.

The study’s sample and methodology are not linked so I suspect a huge bias, in that the projects succeeding sans-Agile have been successful without it long term, while the Agile projects chose Agile because they were unsuccessful pre-adoption — you don’t adopt agile if you were already successfully delivering projects.

The EU should take Apple to court over this for violating the GDPR.

If they aren’t deleting user data the user has deleted, especially old data that should’ve been flushed from all redundancy and resiliency measures years ago (backups, indexes, caches, etc), then they should be fined billions.

Yeah, downvoted. People shouldn’t be writing articles about these things if they don’t know, research, and validate basic info.

Great job “democracies”! In allowing “intelligence” agencies and capitalism to profit from both war and mass surveillance; dictators, criminals, and terrorists (both foreign and domestic) can now purchase big brother oppression tools the Gustapo and KGB could only fantasize about; only limited by how much money they have or promise to generate for the oligarchy.

We also enabled additional anti-competitive features — we think you’re gonna love it!

FOSS has spent the last few decades operating under the assumption that companies would give back for the greater good if they found value and grew dependent on a project. What they didn’t understand is that corporations are parasites who only care about immediate profits, and are more than happy to abuse the honor system indefinitely. There isn’t any benefit to FOSS to continue operating under this model, which is why FOSS is shifting away from licenses that permit leeching for profit.

It’s no different to how corporations have worked to destroy the social contract, and do everything imaginable to evade taxes, offshore labor, corrupt our political systems, and not give back to the economies that incubated them and enabled their success — at some point you have to tell them to get fucked, stop being a fucking parasite, and pay their fair share… If they don’t give back and improve things for the majority, they don’t deserve to profit from it.

The erosion of privacy was always an absolute certainty once Apple started the transition to becoming a service-based company, and why I only choose Linux-compatible cross-platform apps and services for everything essential.

Apple fanboys (or paid guerrilla marketers) have downvoted me every time I point this out, and I’m sure that will continue… indefinitely.

They won’t hand much, if any, user data to Google with this deal, but the profit multiplier promised by predictive analytics guarantees the endless march of surveillance capitalism will continue.

Laws are only for the proles. The oligarchy have free reign.

Get it?

You need to get the pro if you want USB 3 transfer speeds, lol.

You should only use storybook if you are going to share components across devs/projects (+ learning ofc).

I don’t know why you’d duplicate the store. Just write centralized mock constructors once and use them for both storybook and tests. Ideally test the storybook components, so they always stay up to date with changes, but that was relatively new when I used it a couple years ago so I don’t know if they’ve ironed out the kinks yet.

There’s also no way to validate that Apple’s E2EE operates as stated. They could have added a backdoor for themselves or “intelligence” agencies, and we have no way of knowing other than “trust us”. Even if the source code is ever leaked (or a backdoor exploited by hackers), it could be written with plausible deniability — in such a way that it could be interpreted as unintentional (a bug/error).

This is why you should never trust closed source code with your sensitive data, and encrypt it yourself using open source, widespread/trusted, audited tools before uploading it to someone else’s computer.

https://cookbookmanager.com/