iMerNibor

I personally have a access_by_lua script that counts accesses per ip and applies a (very generous) rate limit If the limit is reached the user will just be presented with a page explaining you hit a rate limit and a button that runs some javascript to verify you're not a bot which in turn whitelists the user This strategy has worked really well so far - havent been a target of too bad things yet though. Its a very good and cheap way to go for smaller sites though

Under the assumption the keys would be revoked it's just trash anyways - it'd have been useless anyways, but apparently they didnt realize how serious stuff was, otherwise they would have revoked it A month is plenty of time to change critical S3 credentials

What if he hadn't found out about it, but someone else had already taken the files?

Facebook might've never known

http://www.google.com/teapot :D

It's pretty stupid what they try to do to get even more money

They somehow managed to get a law in place which prohibits quoting of even small passages online (i.e. Google News) without paying for it. What did Google do? Simply removed them from the results, they tried to sue and lost. Now they gave Google permission to include them for free. What about the smaller services? Who cares about those - loads of news aggregators shut down in response.

Now that (some) adblockers have been ruled legal they sued a bunch of people (youtuber, the adblock forum) for providing instruction on how to get around the anti-adblocker wall they put in Fun times

Which is basically the reasoning behind bidding 1$ then..

He got a lot of attention from just doing that aswell, so a success for him

It's too time consuming to figure out which patches to apply to be able to maintain it rather in case any security issues pop up

They do. Evolution.

They needed to evolve to reach a certain age ( -> once they cant reproduce anymore) without dying to cancer. https://www.youtube.com/watch?v=fMMPKJFYzdY for a more in depth explaination

Well, most of the gimmicky levels are easy to explain People have a chance to easily play around with stuff that was just not normal now. Flying around with the clowncopter and shooting things for a whole level is not what you really get in normal mario Same goes for the autoplay levels - just watching something that's crafted to complete itself in (sometimes) astonishing and carefully crafted ways is nice to watch.

I suspect this is gonna die down quite a lot as people get used to it though - it's fun now cause it's new and unusual. It is going to get boring at some point though

Not to mention good level design as you'd see in mario games is hard for people who've never done it

Warning: in_array() expects parameter 2 to be array, null given in src/Kaydo/CloudAppsBundle/Controller/AngularController.php at line 103 500 Internal Server Error - ContextErrorException

If the old web server is going to be up anyways, why not just reverse proxy responses to the new one using nginx for example?

> The bigger sites will already have set up such a system

The main issue what that is you need to pay a lot of money if you visit a lot of big sites and dont like ads

5$ a month for one service vs. 10 or so is a big difference

The huge advantage of making reusable code, even if you never reuse it, is that it's clean and decoupled from the other parts of your application. Thus it'll be easier to understand and to deal with - you won't have to look over what dependencies might cause unwanted effects here or there or what might be able to go wrong in case X. With decoupled code you only need to make sure it does it's "one" (main) function properly.

It also prevents code from turning into spaghetti when adding "special" cases

and barely any support besides incident handling and sales questions ;)

"Privacy

Google maintains the Safe Browsing Lookup API, which has a privacy drawback: "The URLs to be looked up are not hashed so the server knows which URLs the API users have looked up". The Safe Browsing API v2, on the other hand, has the following privacy advantage: "API users exchange data with the server using hashed URLs so the server never knows the actual URLs queried by the clients". The Firefox and Safari browsers use the latter." https://en.wikipedia.org/wiki/Google_Safe_Browsing#Privacy

So, from what I gathered it's just the favicons of the search engines, some mozilla country stuff (not sure why) and google safe browsing (which you can turn off and is a good feature for casual users) So what's the issue here? All this isnt really a problem and safe browsing is, in my opinion, even good for normal users.

Oh no that's not possible. Think of all the politicans who couldn't do work.. That's unacceptable!

Compared to the thousands of songs he'll most likely regularly listen to (I do) it's still cheaper - especiall when your music interest shifts. Not to mention being able to just listen to whatever without having to spend any extra

It which point the news agency could make a big deal out of it, probably not worth the hassle. I mean you can search for bad stuff about google on google and find results - they havent filtered that either

A few years ago when I upgraded to a new more powerful box at my hosting provider I noticed half a year later the old one (which I had whiped and done some testing on after transfering) was still chugging along, serving the silly 403 page I set up. After a few days of talking to the confused support it got shut down.