Illniyar

Probably got better publicity with this ban then if they actually showed the ads.

My money is that this is manufactured by some PR team.

Possibly the Ad's text was purposely inflammatory (something like "overthrow the patriarchy" or something) so that they can say it was banned.

I've made this little side project to get exposed to popular music from around the world.

Basically every week I take the top songs for every country and filter out artists from out of the country.

I've found some songs I really like. Thought it'll be nice to share. There's also spotify playlists there.

More load does not just mean needing to increase capacity, which would be simple for Microsoft to do.

Additional load reveals limits and breaklines that were never known before - your temporary integer IDs are suddenly too small, you reach the maximum file descriptors in a Linux distro, your hash function suddenly has repeating conflicts, your DB index is suddenly oversaturated.

Having massive exponential growth of your traffic would probably require constant refactoring to meet the ever changing system limits.

They are supposed to make sure this doesn't happen. Or if it does have better recovery.

Don't skimp on maintenance, make sure you have planes that can do divert in time.

If there was engine troubles in the middle of the ocean would it still be okay?

I have never worked in a company where it is okay for production to be down at any time. Critical hours or not.

And if production is down even if there is just one user, it is all hands on deck.

No it's not. If the development pipeline breaks on Saturday night there is absolutely no need to go fix it right away.

You should have a method to deploy hotfixes to code that bypasses your development pipeline though, in case the development pipeline breaks while you need to fix production- because you must be able to fix PRODUCTION even if your dev pipeline is broken ( because again your dev pipeline, while important, is not production)

This is a pretty weird article/movement. The greatest hurdle is almost definitely a domain name, which if you want to own the content you have to get. Which even the cheapest would cost you around 6$ a year. (I'm ignoring the "tk" tld, which is kind of a honeypot)

And you can host for a static site for free in a million places. CDNs free tiers are enough for individuals.

I don't get the preoccupation with hosting your own server, what matters is that you own your own identifier (in this case a domain name) whatever it points is vastly less important.

Ostensibly you've ran git before and never saw something like that, seeing a security warning on running git should raise some eyebrows.

you would only need to open it to be exploited, not edit or prompt. Allegedly

It's pretty weird for cursor to run arbitrary exe file without prompting, and alarming that the researchers did not get a proper response for months.

But the example with calculator is a bit misleading I think, you'll have to have a malicious exe already in the system and downloaded, and if cursor tried to run my understanding is that ACL should immediately kick in and you'll be asked for permission to run a new, unsigned app for the first time.

You'll have to have ACL disabled completely for this to be exploitable.

The article headline makes it seem like the factories couldn't make the gloves.

But further down it says that the cost was double and factories couldn't get buyers.

These are very different failure modes, and speak to very different solutions.

I think Fable is predisposed to try and verify it's changes. Which is a very good thing. It takes a lot of prompts to get Opus to do what Fable does unprompted.

That is exactly what I would want from a junior developer - make sure the bug exists, find a way to fix it, verify the bug is fixed.

The problem, as was correctly identified in the blog post - is that instead of stopping and asking for elevated permission it relentlessly tries to find a hack on it's own. (An equivalent situation for a human developer would be needing some access to a third-party sandbox, and instead of asking a senior for credentials, tries to setup his own sandbox from scratch)