v1.30; last modified 2007-05-16 19:14:45 EDT by sjk
?Leave your questions here, and I will answer and organized them.
You probably have multiple desktops running and another users is running a copy of Safari. That person needs to login and quit Safari. Optionally, you can restart the machine -- that will definitely quit all running copies of Safari.
No. If you were goodly enough to pay before registration was required, consider yourself exempt. Go ahead and click the "I paid" button with impunity.
They are blocked by default in v2.x - you can toggle the rule on or off to your liking.
PithHelmet uses a common software package PCRE (Perl-Compatible Regular Expressions) to do its pattern matching on the URLs that Safari attempts to load.
The list below is a series of links to other web sites that describe how regular expressions work.
NOTE: A fix-it tool is included with v0.7.3 and later that should correct this problem. Please see the included installation notes for more information about the tool.
The PithHelmet preference pane should be located in Safari Preferences (Command-Comma). (see the screenshot)
For reasons I don't quite understand, occasionally after an upgrade, Safari will refuse to recognize the newly added PithHelmet preferences pane. Luckily, the work around is simple.
~/Library/Preferences/com.apple.Safari.plist file (either by trashing it, or moving it out of the Preferences folder). This will reset your Safari preferences to the factory defaults. You will have to manually restore them using the Safari preferences panel.com.apple.Safari.plist in an email, that would help me track down the problem.If the PithHelmet icon does not appear on the right side of the toolbar, please feel free to contact me via email.
Yes. Google Adwords can be blocked quite easily. (block googlesyndication.com)
Only with PithHelmet 2.0. It's also tricky - it depends what you mean byreformat However, the new PithHelmet engine is quite powerful and can mutate quite a number of things about a web site as it comes streaming in.
?The way PithHelmet works is not really compatible with Mozilla/Firefox/Camino. However, there is an excellent free plugin called AdBlock for Mozilla/Firefox that does a pretty good job. You should be able to copy/paste the default PithHelmet rules in to AdBlock
.
OmniWeb
has its own content filtering system/ad-blocker. Even though its based on WebCore
, as is Safari, PithHelmet is built on a higher level API, WebKit
, which OmniWeb
does not support. Some PithHelmet rules can be rewritten for use in OmniWeb
, but I haven't tested this extensively. I don't have any plans to support it further.
Yes. Most people have complained about the lack of control for link underlining. Here's what you do:
~/Library/Application Support/Safari Enhancer/linkcolours.cssThat will do the trick.
In 2.0, there are two ways. First way it to modify the Default Site Rule and uncheck "Enable Plugins." The second was is enable the Flash rule in the rule editor (there is a small checkbox next to it in the rules list.
PithHelmet has always had to load the full page before hiding/collapsing blocked content. It doesn't wait for ads to load per-se, just the page itself. If there are ads that don't match the block rules (perhaps because images are linked to a blocked address instead) it might appear that there is a wait.
Most of the time, no. If a URL matches a block pattern, Safari won't be allowed to make a connection to grab the image. There are some cases where the URL doesn't match, but is instead linked to some ad web site. In this case, PithHelmet may look at the link once the image has been downloaded and hide the image from view.
Certain versions are not, though the latest version of Saft (7.5.3 I think) should be.
I've seen this happen a couple of times. It is usually accompanied by some entries in the Console which might look like this:
2005-03-11 19:15:23.438 Safari[446] Uncaught exception - *** -[NSURL initFileURLWithPath:]: nil string parameter 2005-03-11 19:15:23.438 Safari[446] *** Attempt to remove unrecognized exception handler 0xbfffd0d0
I've never been able to reproduce this on my machine, but it's happened to a couple of people. The cure is usually to reinstall PithHelmet. If this happens to you, if you could send me a bug report with the output of this command in the Terminal.app:
ls -lR /Library/Application Support/SIMBL/Plugins/PithHelmet.bundle
that would be swell.
Go to Table of Contents