irotsoma

And this is the same reason why encryption backdoors would basically make encryption worthless. Doesn't matter how strong the metal/encryption is if a backdoor exists to be the weakest link.

Are you wanting something that you don't have to download from GitHub yourself (so a project that hosts a docker container somewhere and just code is in GitHub is OK), or are you looking to boycott any project that is not boycotting GitHub and so any part of that project should not use GitHub for any code at all in which case possibly even dependencies should not be on GitHub even if they publish their distributions elsewhere? Or somewhere in between?

Local storage backups (local to the servers wherever that is, so "relatively local") should be the initial backup, then those backups should be what's synced to the off-site/third-party provider, generally. But it really depends on the types of tech and how those backups are generated.

If this was a self-hosted forum, yes, that's an option. But for professional purposes, a dedicated off-site backup provider is better than having storage at an office site.

Not too surprising. Data backups need to be with different providers. The article seems to think it's not "putting all your eggs in one basket" because the provider had redundancy. But that's not much different from storing physical backups locally because they were stored in a fire-proof safe. Sure you made backups, but by storing them in the same building as the servers means the same disaster that could take out the servers could take out the backups. A "fire-proof" safe will protect it from some things that won't protect the servers, but there are still types of disasters that could take out both, like a big enough bomb rather than just a fire.

What if AWS went bankrupt and the servers were repossessed and sold off with the data spread across all the different new owners of the disparate data centers? What if Amazon just decided AWS was no longer profitable and shut it all down.

Sure that's not going to happen to AWS right now because it's hugely profitable, but a serious US market crash combined with a major escalation by the current administration in the increasing surveillance state in the US which could kill the trust in the company, cause a massive migration to EU based companies and cause the subsidiary company that holds the data to go bankrupt without necessarily killing Amazon as a whole. Those subsidiaries often "run at a loss" even with extremely high income in order to divert profit to shareholders, claim tax breaks on "losses", and eliminate liability to the main company.

The legal proceedings of bankruptcy or other events could put the data in legal limbo for years before it's accessible again.

I've seen some, but it's way, way less common than the major corporate platforms, but since there's no pay and no ads to make money off of, it's not too surprising. As the article briefly mentions, there's just too much monetary incentive to make junk vs quality content on most for-profit platforms.

Glad I don't rely on their stuff because the support is about to get enshitified. The company I work for does though...so...

Usage is rising because corporate executives started getting kickbacks and thinking they could cut staff by implementing it. But developers who have actually had to use it have realized it can be useful in a few scenarios, but requires a ton of review of anything it writes because it rarely understands context and often makes mistakes that are really hard to debug because they are subtle. So anyone trying to use it for a language or system they don't understand well is going to have a hard time.

This is why I never used their images for any of my projects and do everything I can to use official charts made by the software vendor itself or create my own and put them in my personal git repo for automated deployments.

Any business that gives away middleware for free, likely does that in the hopes of monetizing that pretty directly and eventually will be pressured to increase monetization of those things by those investors or will be forced to stop developing those products due to lack of funding. Middleware really doesn't have many other good ways to monetize.

I have yet to have an AI write code of more than one or two lines that doesn't have a breaking bug. Speed isn't useful if it's broken. And honestly I usually spend more time debugging AI code than I would have just writing it myself. It's nice sometimes for getting an understanding of syntax of a system I'm not used to, but beyond very generic scripts that don't depend on context, it's pretty useless in my experience. I have Copilot integrates with my IDE for work and it's more trouble than it's worth so far. Even just for code completion, the IDE does a better job most of the time even if it suggests much smaller chunks at a time. And the smaller chunks are actually better if I have to proofread every single word either of then outputs anyway.

Can't convince a conservative that women and POC still make less money for the same job and affirmative action is still needed, but "AI" knows it.

"[The changes] will impact everyone who uses the internet in Australia – not just people under 16."

I'd argue that these kinds of laws usually only affect people other than the people who are being blocked. The people being blocked will just find alternatives that don't block. VPNs or alternative search engines, etc. The only ones affected are the adults who now have to sacrifice their privacy and allow companies to collect and sell all of their information more easily and governments to build a profile of everything a citizen does without context. Search for information about nuclear reactors because there's a new one being built in your neighborhood and want to know about the risks, and you'll likely immediately get added to the watch list for nuclear terrorism. Add in a search for explosives to get rid of a tree stump in your yard, and now you may end up on a secret no-fly list and not find out until your vacation is ruined. So many implications to context-less search result data collection which is likely the real aim of these laws rather than keeping kids "safe" since it ultimately just forces them to use less safe alternatives.