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.
longer than loading dozens of shit js, tracking pixels and obfuscation code into the renderer?
The moment I can use a cheap edge LLM to reduce the entire page to the few bullet points I care about with optional expansion of content I don’t really care much anymore about render timing - the ultimate cost on us is extraction the information we want from the page, which is getting more and more enshittified because our attention is being sold.
I see your point. Getting the pattern from DOM to create something custom is possible but not in real time. We can not just rely on that. Finding pattern is good but relying on that is not
can't we adapt this to other forms of ads, meaning changing visuals to a height x width of 1x1? This will not save bandwidth, but 'their' algos still assume we're loading and displaying ads.
Yes you are right they can do this but it's not that easy to do and also these big tech giants can't just simply update the code like we can. Everything goes through a process which takes ample amount of time and If they does it also, I will come out with some more solution.
Last I checked, IPFS still leaks the IPs of hosters, so it's a no-go for a CDN if an attacker can just DDoS the target to take them offline (and oops, then IPFS can't help if new content isn't being pushed into some provider).
IPFS needs anonymous peering or it's not going to be a decentralized CDN, only a decentralized load balancer for static assets.
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'm working for a tech firm in one of these two related areas. The idea of bringing the work computer home sounded good until IT added a number of high-bandwidth sites to the IT-mandated DNS blacklist software to keep traffic down for remote workers.
I could see things like Hulu and Pandora being less mission critical than other sites but then they blocked YouTube and, probably because google mixes domains a lot, gMail got caught in the net. People were not happy about that.
I don't know either. The backlash has been really amusing.
It's ranged from engineers claiming they can't work without streaming music to backend office staff saying they need YouTube to help them understand how to work Microsoft Office.
gMail is an interesting edge case, though. I keep a tab open all day long as well as do probably a lot of people. But it's not for company business so it seems like that's not a place to complain. But people are.
Seriously, to any of you CEO/CTOs tuning in out there: the next time you're lining up a RIF just block Netflix for an afternoon and tag the people that complain to IT. There's your low-hanging fruit.
like sometimes you need to check something on your personal accounts, but that's usually a one-off to do with a private browser. anecdote: i applied to grad school and got a reference from my boss but there were some issues and had to log in to the school account to check things.
that said, unless you're in a secure or radio-free facility use your damn phone.
Some of the FedRamp standards require a VPN and prohibit split tunneling (i.e. Spotify goes directly out to the internet and the VPN only exposes routes to internal company hosts).
AFAICT, most of them allow split tunnels for work VPN -- most work VPNs are set up to allow access to corporate resources, not block normal usage. Some places have very high security requirements.
I’ll assume that they’re VPN’ing into work and their IT doesn’t allow split tunneling. As a result, all traffic has to flow into the VPN concentrator as a bottleneck.
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.
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.