Jentic co-founder here. Right now, you've got to do a PR, but we plan to monitor the web for new OpenAPI documents and automatically load them in within 24 hours.
Once ingested, we will monitor the original URL for updates. We plan to enrich ingested OpenAPI docs with any additional information we can find on the web (and live agent telemetry). These enrichments will include some spec extensions for additional info agents need (e.g., how to enrol/authenticate, rate limits, pricing, licensing, trust & safety, side-effects, rollback etc).
We will be careful not to clobber any 1st party docs with AI content, and to intelligently merge any AI enrichments into future versions.
Note that a lot of APIs do not have good OpenAPI documentation, and so we'll be generating those from scratch.
In addition, we have an agent that reads any OpenAPI specs in the repo, generating potentially useful workflows composed from OpenAPI operations and other workflows (with all workflows represented in Arazzo specs). That where all the Arazzo specs currently in the repo came from.
MCP is ideal for agents to connect to services, but is not designed to represent the depth of API knowledge we are aiming to represent (and it would be worse at its primary job if it tried to). We will shortly release our own MCP server that provides agents with convenient access to interact with this API repository over MCP. For example, to search for operations and workflows that fit a current sub-goal, and to load details so they can more reliably execute a chosen operation/workflow (assisted by a OSS library we'll release soon) and to interpret the responses intelligently.
Jumping in here as we produced that data. Global average is about 5%, but in US & UK it's about 15%. In much of Europe it's about 2X that. If you have a technical audience, 20% - 30% adblocking is now normal. If you are gamer-focused, 40% - 50% is normal.
The growth isn't driven by technical people any more; it's normal people who've grown up using web browsers and who don't think twice about installing an extension on Chrome. You're correct through that it is spreading through word of mouth. You can get more on the pagefair blog.
Fair points. We need to provide the source data and a full explanation. We're going to publish a detailed report in August with everything in it.
To answer one of your questions, the predicted desktop rate is based on an assumption that adblock adoption is driven by word of mouth (we have a basis for this assumption), and a compound growth rate is fitted to raw adblock rate data.
It's hard to combine the google trends data into the same model, because it's just a picture of search volume, not total adblock installations. I think it would be a fair to assume that the growth rate of new installations would match the growth rate of search volume, which means that the growth rate of 65% we're seeing this year is higher than it would have been in previous years.
Finally, I want to acknowledge that nothing can grow exponentially forever! At some point everyone who will use adblock will already have it installed. I'm pretty sure some countries are pretty close to adblock saturation already (Germany, Poland, Sweden and Finland).
I used to block ads before we noticed that 30% of our website revenue was lost to adblocking. We realised that people weren't intentionally blocking ads on our site, but probably due to some bad advertising that pushed them over the edge somewhere else on the internet. There was nothing we could do, so started a new business (PageFair).
In your post, you are correctly angry at advertisers. But adblocking doesn't punish advertisers, it punishes websites, starting with your favorite ones. Right now, the advertisers just go somewhere else for their traffic. Even if it did somehow punish advertisers, would it discriminate between the relevant & polite ones (e.g., job ads on stackoverflow) and the spammy ones (magic weight loss pills on dictionary.com)?
Agree that the publishers and web users need something better. That's our goal at PageFair.
Adblock Edge is included, as is every plugin or proxy that acts to remove advertising from web pages. Unfortunately, we can't specifically distinguish adblock edge from the others right now.
Only text and/or static images with strict limited on how they are displayed so that they are not annoying or intrusive. No scripts, so no viruses, and no third party trackers or creepy stuff like that either.
It's easy. If you ever see one of our ads, you can permanently opt out using the close button. We're working hard not to show the kinds of ads that most adblock users would want to block. We currently have < 1% opt outs.
We think (@pagefair) it's clear that adblock is being promoted just fine by word of mouth. It's the ad industry that's got to change somehow. We're trying to be part of that. What's shocking to us is how the ad industry mostly doesn't even recognise how fast adblock is growing. To them, it just looks like more people have switched off their PCs, because they just can't see that segment of the audience anymore. Therefore, they're having a really hard time figuring out that this is even happening to them.
From the publisher's point of view, ads are the only realistic way that they can pay for the expense of running their websites. The alternatives are paywalls, which don't work, or shutting down (which a bunch of sites that were using over the last year ended up doing!).
Anyway, most people install adblock because of really crappy ads that get in your face. Do you have a real problem with static image banners that don't get in the way of content?
What we found most surprising was the growth rate - 43%. If this keeps up all ads will be blocked by 2018!
Of course, this won't happen. But it looks like things are set to get a lot worse for publishers before they get better.
Oh, and blocking rates on mobile/tablet is very low, probably consisting of ISP-level adblocking. That will shortly change though - the adblock community is hard at work creating mobile versions.
The rate is actually highest on gaming-related sites. I guess that audience is usually sufficiently technical, and is also habitually bombarded with aggressive advertising.
Not so far as we are aware. Not many sites have gone down the whitelisting route, for the kind of reasons discussed in the post above.
That said, lots of our customers are discovering just how badly they are affected. Some sites have more than 64% of their visitors blocking their ads, and are facing extinction.
We're using 10% as a very conservative estimate actually. We've been measuring adblock data for 9 months now across several hundred sites, many of which are very large. The current average blockrate across all these publishers is 26.1%. These are the guys who are so acutely affected that they signed up to us in the first place, but it gives you a good idea.
A fair estimate of a minimum value is the block rate on sites that are non-techie, e.g., lifestyle (12% blockrate) and news (16% blockrate).
We'll be doing another post soon revealing all these numbers and our methodology in collecting them in detail.
Once ingested, we will monitor the original URL for updates. We plan to enrich ingested OpenAPI docs with any additional information we can find on the web (and live agent telemetry). These enrichments will include some spec extensions for additional info agents need (e.g., how to enrol/authenticate, rate limits, pricing, licensing, trust & safety, side-effects, rollback etc).
We will be careful not to clobber any 1st party docs with AI content, and to intelligently merge any AI enrichments into future versions.
Note that a lot of APIs do not have good OpenAPI documentation, and so we'll be generating those from scratch.
In addition, we have an agent that reads any OpenAPI specs in the repo, generating potentially useful workflows composed from OpenAPI operations and other workflows (with all workflows represented in Arazzo specs). That where all the Arazzo specs currently in the repo came from.
MCP is ideal for agents to connect to services, but is not designed to represent the depth of API knowledge we are aiming to represent (and it would be worse at its primary job if it tried to). We will shortly release our own MCP server that provides agents with convenient access to interact with this API repository over MCP. For example, to search for operations and workflows that fit a current sub-goal, and to load details so they can more reliably execute a chosen operation/workflow (assisted by a OSS library we'll release soon) and to interpret the responses intelligently.