mohamedmansour

Pretty lean extension, you basically set the playback rate of an Ad to 16 and automatically click on skip ad when it appears.

If this becomes popular, Google can copy Facebook anti blocker methods and just randomize the classnames and Dom depth of nodes for the button. And they could honey pot it with hidden elements or image buttons.

This is exactly why IPFS is needed! Decentralized CDN.

No excuse converting python 2 to python 3 slowly. One commit at a time. We did that in Chromium. Using newer Jon deprecated, unsupported libraries brings a bit better team Morale and enjoyment in what you do. Imagine intern coming in, and using Fortran.

I might bring my work computer home then!

TLDR; “Used bufferapp API to post all social networks

You don’t, behind the scenes they use orchestrations like kubernetes or service fabric. So much easier deploying a docker container as a Azure Web App, so easy to auto scale based on thresholds of certain resources, so easy to debug what’s wrong since they give you all the tools. I use that in my current projects today.

But Azure Kubernetes in my last project was easy too, it comes with a sophisticated monitoring solution, it integrates nicely with cheap Azure Load Balancer, but still too much overhead than Azure Web App.

That’s amazing work Lebron did, he didn’t shut up and dribble.

Doesn't work on Edge, Firefox, or even Safari. I am sorry, your first sentence "big believers in standards" is just a lie. It is just developer laziness for supporting non standard stuff and doing User Agent sniffing.

Rule #1 is do feature detection not user agent detection. What are you doing that is "pretty deep in the browser"? NaCL? Experimental Chrome features?