• 0

Chrome Beta Adblock extension.


Question

Came accross this, thought maybe useful for those keen by deterred by no ad blocking. So far so good from my testing it's blocking them well:

So it has finally happened, Google has begun to open the ability for extensions to be added to Google Chrome (although it is limited in scope). We have been playing around with the documentation since reading Matt Cutt’s post the other day. On our first project, we decided to modify our earlier Adblock code. Now it can be installed in Google Chrome automatically. It’s now a set and forget application. If you’re interested in upgrading to it, we’ll explain how(trust us, it’s easy as pie). Then we will show you how to start making your own extensions (or at least where to start). One quick note, you need to have a recent developer build or Google Chrome 2.0 beta. So let’s start.

First, to be enable the support for extensions, you will need to edit the target field of the shortcut field you use to launch Google Chrome. To do this, right-click on the shortcut, select “Properties” and add to the target field the following information : --enable-extensions --load-extension="c:\extension"

What this does, is allow Google Chrome to know where your extensions will be loaded. Now you actually need to create that folder on your C drive. Do that by adding a new folder and naming it “extension”. Next download this file, it is the Adblock script. Unzip and drop the files into “the extension” folder. That’s it. The next time you open Google Chrome all ads will be blocked–even defeating current Adblocking blocking scripts. You can verify the load properly by typing chrome-ui://extensions/ into the Chrome address bar. To disable you will need to delete the files from the extension folder.

Just so you know there are two files needed for every extension

The first is something called manifest.json , it will look like the below:

{

“format_version”: 1,

“id”: “00123456789ABCDEF0123456789ABCDEF0123456″,

“version”: “1.0″,

“name”: “My First Extension”,

“description”: “The first extension that I made.”

}

Here is some information on what these keys do:

* format_version (required): Tells Chrome which version of the manifest format to use. Right now there is only one version, and it is version 1. (NOTE: Maybe we should just remove this, we can always add a format_version key later if needed).

* id (required): A unique ID for the extension. Right now, this can be any 40 digit hexadecimal number, but in the future it will be a SHA-1 hash of the extension’s public key.

* version (required): Is the extension’s version. You can use any number of dot-separated numbers for the version.

* name (required): A human-readable name for the extension. (NOTE: In the future all these human-readable texts will have to be internationalized).

* description (optional): An optional longer description of the extension.

Content Scripts is the next portion. A content script are JavaScript files that run in the context of web pages the browser loads.

You can read the rest of details here, but remember it’s still early in the development. There will be a more developed .CRX extension file formats for Chrome, and an ability to have more than one extension loaded at a time. In short, there is still much work to do. Furthermore, as time goes on the documentation will change, but the benefit of being involved early will help you get a jump start on competition. Good luck on the tweaking!

As an extra, this is our “fun” script. You can load this over the files current adblock one. See what happens when you visit Google.com with it installed. There are tons of possibilities with this…Let your imagination go…

***Note about Adblock***

I know some may find it funny that an e-marketing blog has an Adblock Script. It’s not an oxymoron. We know its a matter of time before an Adblock for Chrome is created, so we might as well be there first to find creative ways around it (hence our “fun” script). We support smart marketing, where annoying pop-up and distracting ads are not part of a website. That’s what this blog and our company is about. And we also know reality from our studies. Those who are comfortable enough to implement this solution will not typically be the people who click ads. Nevertheless, we must warn you, installing this script is a nuclear bomb. There is no off switch unless you delete the files. You are also depriving many sites of revenue when you use it. Please use this only as a starting point for your own development and maybe someone (or we) can work out an easy way to enable/disable the script without folder deletion to turn it off.

http://www.mark8t.com/2009/03/20/creating-...ock-for-chrome/

Link to comment
https://www.neowin.net/forum/topic/750116-chrome-beta-adblock-extension/
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
    • Camtasia 2026.1.3 by Razvan Serea TechSmith Camtasia is the complete professional solution for high-quality screen recording, video editing and sharing. Camtasia 2026 makes editing your videos easier, and faster than ever. The new editor is packed with enhanced video processing, all-new production technology, an innovative library, and stock videos and other creative assets to help you create more polished, professional videos. No video experience needed. Anyone can create informative, engaging videos. Create professional, eye-catching videos: Add special video effects - Apply Behaviors that are perfectly designed to animate your text, images, or icons. Get a crisp, polished look without being a professional video editor. Drag-and-drop your edits - What you see is what you get. Every effect and element in your video can be dropped and edited directly in the preview window. And you can edit at resolutions up to beautiful 4K, for clear video at any size. Get exceptional performance - Camtasia takes full advantage of your computer’s processor with 64-bit performance. You’ll get fast rendering times and enhanced stability—even on your most complex projects. Camtasia 2026.1.3 changelog: Feature Updates Improved keyboard navigability in tool panels. Improved screen reader accessibility of headings in Preferences. Tool panels can now be resized using a keyboard-navigable control. Updated color of folder icon in User Library tab for better visibility. Grouped media now render a composite waveform considering all audio media within that group. Added Long Path Aware to the manifest of Editor and Recorder. Performance Improvements Improved performance for editing groups on the timeline. Improved the project loading performance when timeline has lots of trec media with cursor data. Updates for IT Administrators Updated cpp-httplib from 0.38.0 to 0.43.3. Updated expat from 2.7.4 to 2.8.0. Updated freetype from 2.13.3 to 2.14.3. Updated harfbuzz from 13.0.1 to 14.2.0. Updated libpng16 from 1.6.55 to 1.6.58. Updated pango from 1.57.0 to 1.57.1. Updated girepository from 2.86.3 to 2.88.0. Updated pcre2-posix from 10.47.0 to 12.0.2. Added new harfbuzz-gpu.dll. Updated FFmpeg from 7.1.1 to 7.1.2. Updated aom from 3.11.0 to 3.13.1. Updated dav1d from 1.5.0 to 1.5.1. Updated ogg from 1.3.5 to 1.3.6. Updated SDL2 from 2.32.4 to 2.32.10. Updated zlib from 1.3.1 to 1.3.2. Updated Nalpeiron binaries to version 4.4.69.3. Bug Fixes Fixed an issue which prevented some user submitted crash reports from being sent. Fixed a potential memory leak when decoding HEVC or VP9 video. Fixed a potential crash when trying to delete a range selection on a magnetic track. Fixed a bug with the Properties Panel showing stale properties when only a caption is selected on the timeline. Fixed an issue that could prevent the Opacity and Blur properties from being changed in the Background Removal effect. Fixed an issue where larger Camtasia online projects may fail to open in Camtasia Editor. Table of contents thumbnails are no longer created for Smart Player exports with no table of contents. Fix resetting skew revert to revert just skew and not scale as well. Fixed editing in Snagit with snagX file with Unicode characters. Fixed a bug where grouped visual media could be cropped in some cases. Fixed importing SnagX files with Unicode characters. Localization fixes. Download: Camtasia 2026.1.3 | 309.0 MB (Shareware) View: Camtasia Homepage | Tutorials | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      188
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!