It’s going to flop, but that’s ok because they only bought one lot from the Chinese factory

I doubt it. They could expand the list of allowed content, but Apple has a right (and responsibility) to moderate the content on their platform

Delaying the review process is just petty, but lawsuits are only profitable when you win, so Apple denying the app would mean Epic wanting another lawsuit.

You are correct! And moreover, fragmentation was bad on HDDs because they are good at reading sequential data, so fragmentation limited performance by making reads more random. However, SSDs are the opposite and are more performant on random reads, so fragmentation actually benefits them! (some of the time)

They thrive now, but they will never forget the Wii U

In close collaboration with Valve

Sounds to me like they will open it to other manufacturers, but this could mean that they are releasing it publicly also. I’m excited!

Normally I would say that Microsoft wouldn’t care and they would just make an exception, but after the CrowdStrike error, they might be just a little bit more careful. Or maybe I have too much faith in them

The nice thing about the fediverse is that you could start your own instance and not federate with them

So they’ll be playing on a higher difficulty?

Accidents happen, and people panic. Maybe she thought she was pressing the breaks and made the problem worse. I highly doubt anyone would do it intentionally.

Ignoring the problem doesn’t make it better

On top of this, someone could make an instance dedicated to that niche subject and similar topics, and you could subscribe with the account you already have somewhere else instead of having to periodically check that niche instance.

Right now the problem is finding those instances, and generally finding reliable instances that won’t suddenly go offline

From the app no. Even if you could get into the pokemon go app and mod it, they would quickly notice the modified app and ban you

It will be next year

This was a series of decisions with good intentions that went poorly in the long run.

Our customer wanted us to setup a system so their users could track their products from their site from a variety of carriers; but their backend was very old and difficult to work with, and their network very locked down.

We were struggling to setup a single carrier, so we eventually decided to setup a new server with modern tooling on our own network so we could develop this and other “complicated” features with less pain, and they would only have to make a single exception to their firewall.

Fast forward a year and:

• They didn’t request any more “difficult” features, so the server was serving a single API
• One of our carrier’s API keys had expired and nobody noticed because they weren’t using it, and they didn’t request support for additional carriers either
• Somebody on their security team noticed the strange calls to our servers and demanded we moved the API to their infrastructure anyway

look up the difference

Sounds like too much effort

Let’s see: 30*3 = 90

We have room for 3 more categories, and then some!

They are all small, but they still make up 100%

There is also a limit to the number of files the browser can download in parallel, so if many files have to be fetched, they have to wait until the previous downloads are finished. This slows down performance even more