-
Notifications
You must be signed in to change notification settings - Fork 83
FAQ
Under construction.
- Can I whitelist Facebook (or whatever) only when visiting Facebook (or whatever)?
- Why my browser-based popup player doesn't play even after whitelisting all?
- What is "strict blocking"?
- In the top right of the matrix, what is "other"?
- How can I see the full URL of requests made on a page?
- What does HTTP Switchboard does more than, say, AdBlock+ or AdBlock?
- What do you gain out of this?
Yes, using per-site permissions.
Typical scenario as an example (inspired from issue #40):
- Goto http://www.teamradio.ca.
- Click "LISTEN LIVE 1040" on the right.
- A browser popup window opens (that would be the browser-based player).
The popup menu for HTTPSB is unreachable in the browser-based player window. This means there is no way to whitelist just what is needed to make the browser-based player work. The problem is not specific to HTTPSB, any extension you have might be crippled by having its popup menu unreachable.
This is why popup browser windows suck. They are rude, they interfere with your choices.
Until I find a handsome solution (if any), here is the workaround:
- Copy the URL address in the browser-based player.
- Open a new tab in the main browser window (the one in which the extension button is not occulted).
- Paste the URL address in the address bar.
- The browser-based player will now open in the full window, you can now whitelist appropriately.
- Once you are satisfied with your careful whitelisting, make sure to persist them using the padlock.
- Close this tab.
From then on, the browser-based popup-up player will be able to play correctly the content.
Just for information purpose, for the above example specifically, just whitelisting:
teamradio.ca
streamtheworld.com
-
plugin
@streamtheworld.com
Solved the problem.
Here are snapshots of the difference between using strict blocking or not.
- Open the popup menu of HTTP Switchboard
- Click on the Stats icon in the top-right corner
- HTTP Switchboard info page opens
- Scroll down to the Advanced stats section
- There you can see the full URL of all requests, blocked or allowed, made by your browser
- Use the drop-down list to select the stats for a specific page
- Use the checkbox filters to narrow to specific types of request
There is AdBlock, and there is AdBlock Plus (which the EFF advise to install).
If you really care about your privacy, it is good to know what is happening behind a web page, so I did some tests to compare AdBlock and AdBlock Plus vs HTTP Switchboard. See the differences for yourself when using real web pages, and make an informed choice:
- AdBlock vs HTTP Switchboard:
- edition.cnn.com (Edit: it appears the diffs are not permanent after all, my original one has been replaced with something else...)
- nbcpolitics.nbcnews.com.
- AdBlock Plus (using EFF installation instructions) vs HTTP Switchboard:
Using out of the box settings for AdBlock and HTTP Switchboard. Using settings suggested by EFF for AdBlock Plus. Note that with HTTP Switchboard, the user does not need to explicitly change the cookie settings in chromium/chrome (as required with AdBlock Plus). If cookies are blacklisted for a domain, any outbound cookie will be removed, regardless of chromium/chrome owns settings.
Nothing, the project is GPLv3. I am having fun doing this though. Oh, and this