I wonder.... - sjk

Which version of PithHelmet, and have you tried visiting www.usatoday.com as a crashed test?

Reply to This

Wednesday, February 09 2005 @ 08:14 PM PST

I wonder.... - dont-spam-me

I'm using the latest version of PithHelmet, v2.2, and Saft v7.5.1. www.usatoday.com opens without a hitch. Maybe I'm just leading a charmed life, but all is well on my G4/933 Quicksilver!

Reply to This

Wednesday, February 09 2005 @ 08:38 PM PST

I wonder.... - sjk

Thanks for the feedback. Did you check cnn.com? And do you have other Safari plugins installed? I also have SafariSource, which is compatible with Saft 7.5.1 when PithHelmet 2.2 is disabled. And Saft+PH without SS is a crasher. On 10.3.8.

What's important to me isn't 7.5.1 but rather ensuring that Saft and/or PithHelmet developers do their best to ensure future versions can co-exist peacefully again.

Reply to This

Wednesday, February 09 2005 @ 10:56 PM PST

I wonder.... - Hao Li

I understand that you want them both. Though both patches Safari and are very likely to crash Safari. Hope you understand that I do not give any guarantee for the compatibility with other plugins. But that does not mean I do not try to avoid the problem, I do test it when bug reports come in.

Reply to This

Thursday, February 10 2005 @ 01:44 AM PST

I wonder.... - sjk

I understand your "no compatibility guarantee" position. Is there a reason this particular Saft modification can't be optional so compatibility with other plugins is restored? I'd ask the same of Mike if he made a recent PithHelmet change that caused Safari crashes when used with Saft or other plugins. Of course, if someone installs the current Saft plugin now and PithHelmet later it may appear to be PithHelmet's problem. But the difference here is a pre-existing compatibility has been disrupted by Saft's change. Now that you're aware of it how you intend to respond is the key issue here.

I recently went through a similar situation with an EyeTV change that caused it to misbehave while CodeTek Virtual Desktop was running. EyeTV changed, CTVD hadn't. Both parties were aware of and reminded several times of the incompability. Many months later another EyeTV change restored compatibility; CTVD remained unchanged.

Reply to This

Thursday, February 10 2005 @ 03:36 PM PST

I wonder.... - sjk

[that wasn't finished; clicked submit instead of preview]

Just wanted to finish by saying that I don't want to appear impatient for an immediate compatibility resolution, especially since I'm satisfied using Saft 7.5.0 right now. But I won't be pleased if Saft development continues while ignoring this specific issue, as happened in the EyeTV/CTVD example.

That's my perspective on this.

Reply to This

Thursday, February 10 2005 @ 03:52 PM PST

I wonder.... - Hao Li

The root of this problem is IDN spoofing detection of Saft does not work together with PithHelmet. Since I think IDN spoofing detection is so important that I want Saft's users to have it (and all the other Safari users to be protected too by releasing a free plugin Saft Lite for it), I have to accept the crashing problem with PithHelmet and wait for Apple to fix the spoofing security problem in Safari.

Reply to This

Thursday, February 10 2005 @ 11:50 PM PST

I wonder.... - Brutal

Thanks for clearing this up. I've now rolled back to Saft 7.5 while waiting for an official Apple security update.

Reply to This

Friday, February 11 2005 @ 04:09 AM PST

priorities - sjk

Let's agree it's a higher priority for Apple to release a fix for IDN spoofing in Safari than you to make Saft compatible with other Safari plugins? :-)

Reply to This

Saturday, February 12 2005 @ 01:15 AM PST