Lot of replication and caching in there. For every cache there has to be a solution for how we're gonna make sure India doesn't receive the cached version, or receives a different cached version than the rest of the world. You also need to be sure that none of your changes are going to cause any significant reliability or performance issues. If you wanted to block India from accessing the entire site you could just cut them off at the top of the diagram, but blocking just one article means you have to get a lot more in the weeds.
Could they have hacked something together in 36 hours? Maybe. But the risk of causing larger reliability issues, or of having the forbidden article still partially accessible in India, would not be worth it.
Yeah, I saw. I was just explaining that it's not just some BS; there are very good reasons why they couldn't put together a well-tested reliable solution with a 36-hour deadline.
There have been only about 6 office actions involving content for that 20 years, so one can imagine it might not be much of a priority to spend an entire afternoon doing something they don't expect to use even once a year.
I can imagine. That's too much to ask to a company that's been on business for 20 years and have received 1.3B USD in total.
I could come up w/ a solution to that in an afternoon on my $5/mo server but yeah "you don't understand the scale of wikipedia" or some bs.
Not "donating" a single cent ever again.