When I try to install BetterPrivacy 1.68 in SeaMonkey 2.6.1, I get the
following error: "BetterPrivacy could not be installed because it is
not compatible with SeaMonkey 2.6.1." I get this even when I attempt to
install directly from the AMO site (not my usual practice).
> When I try to install BetterPrivacy 1.68 in SeaMonkey 2.6.1, I get the
> following error: "BetterPrivacy could not be installed because it is
> not compatible with SeaMonkey 2.6.1." I get this even when I attempt to
> install directly from the AMO site (not my usual practice).
The author hasn't listed Seamonkey compatibility for the latest version on AMO for some reason, I don't know why because its install.rdf still claims compatibility. That probably explains why the redirect is happening but I don't think it explains the installation problem.
> On 01/22/12 11:57, David E. Ross wrote:
>> When I try to install BetterPrivacy 1.68 in SeaMonkey 2.6.1, I get the
>> following error: "BetterPrivacy could not be installed because it is
>> not compatible with SeaMonkey 2.6.1." I get this even when I attempt to
>> install directly from the AMO site (not my usual practice).
> The author hasn't listed Seamonkey compatibility for the latest version
> on AMO for some reason, I don't know why because its install.rdf still
> claims compatibility. That probably explains why the redirect is
> happening but I don't think it explains the installation problem.
Late reply, I know; apologies.
I've just tweaked BP 1.68 to install and run under SeaMonkey. I got permission from NC to release it.
Links:
Direct download (until it lands on the xSidebar page):
I've only done minimal testing under Linux and OS/2, so I'm interested to hear from others.
Cheers/2
-- Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------
> On 01/22/12 03:18 pm, Dave Townsend thus wrote :
>> On 01/22/12 11:57, David E. Ross wrote:
>>> When I try to install BetterPrivacy 1.68 in SeaMonkey 2.6.1, I get the
>>> following error: "BetterPrivacy could not be installed because it is
>>> not compatible with SeaMonkey 2.6.1." I get this even when I attempt to
>>> install directly from the AMO site (not my usual practice).
>> The author hasn't listed Seamonkey compatibility for the latest version
>> on AMO for some reason, I don't know why because its install.rdf still
>> claims compatibility. That probably explains why the redirect is
>> happening but I don't think it explains the installation problem.
> Late reply, I know; apologies.
> I've just tweaked BP 1.68 to install and run under SeaMonkey. I got > permission from NC to release it.
> Links:
> Direct download (until it lands on the xSidebar page):
> I've only done minimal testing under Linux and OS/2, so I'm interested > to hear from others.
> Cheers/2
I finally installed BetterPrivacy 1.68 for SeaMonkey, and it continues
to operate with SeaMonkey 2.13.2. For this, I had to make two tweaks to
the install.rdf file.
The first tweak was in the area
<!--SeaMonkey-->
<Description RDF:about="rdf:#$dLacB4"
em:id="{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}"
em:minVersion="2.0a1"
em:maxVersion="2.6.*"
where I changed maxVersion to 2.9.*. Since then, I have not had to
update maxVersion because of other changes in how extensions are handled.
More important, I had to tweak
<!--em:targetApplication RDF:resource="rdf:#$dLacB4"/-->
at the bottom of install.rdf. Note that this is commented out and that
#$dLacB4 appears both here and in the earlier tweak. By removing the
comment brackets (!-- and --) to make
<em:targetApplication RDF:resource="rdf:#$dLacB4"/>
I was then able to install and use BetterPrivacy 1.68.
I believe the commenting of the targetApplication for SeaMonkey was
intentional, but I do not know why.
> I finally installed BetterPrivacy 1.68 for SeaMonkey, and it continues
> to operate with SeaMonkey 2.13.2. For this, I had to make two tweaks to
> the install.rdf file.
> The first tweak was in the area
> <!--SeaMonkey-->
> <Description RDF:about="rdf:#$dLacB4"
> em:id="{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}"
> em:minVersion="2.0a1"
> em:maxVersion="2.6.*"
> where I changed maxVersion to 2.9.*. Since then, I have not had to
> update maxVersion because of other changes in how extensions are handled.
> More important, I had to tweak
> <!--em:targetApplication RDF:resource="rdf:#$dLacB4"/-->
> at the bottom of install.rdf. Note that this is commented out and that
> #$dLacB4 appears both here and in the earlier tweak. By removing the
> comment brackets (!-- and --) to make
> <em:targetApplication RDF:resource="rdf:#$dLacB4"/>
> I was then able to install and use BetterPrivacy 1.68.
> I believe the commenting of the targetApplication for SeaMonkey was
> intentional, but I do not know why.
I've done that in my modified version, and have cleaned up some of the English in the UI. There's still more to be done, as time permits.
;-)
-- Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------
David,
I worked well for me when I clicked on the first URL. What web browser did
you use? I must admit, however, that I ued the latest Firefox web browser
to do so, and it was on my Android Smartphone that I did this. And once I
wet to that webpage, I copied the webpage URL, which is:
https://addons.mozilla.org/en-US/seamonkey/addon/betterprivacy/
But I was able to get to it. I wonder what error you had and if it had to
do with your web browser's settings as to why it didn't work becaue the URL
itself seems to not be faulty, at all. Hope this info helps, hon. :)
April Morone
On Nov 11, 2012 9:55 AM, "Lewis Rosenthal" <
> On 01/22/12 03:18 pm, Dave Townsend thus wrote :
>> On 01/22/12 11:57, David E. Ross wrote:
>>> When I try to install BetterPrivacy 1.68 in SeaMonkey 2.6.1, I get the
>>> following error: "BetterPrivacy could not be installed because it is
>>> not compatible with SeaMonkey 2.6.1." I get this even when I attempt to
>>> install directly from the AMO site (not my usual practice).
>> The author hasn't listed Seamonkey compatibility for the latest version
>> on AMO for some reason, I don't know why because its install.rdf still
>> claims compatibility. That probably explains why the redirect is
>> happening but I don't think it explains the installation problem.
> Late reply, I know; apologies.
> I've just tweaked BP 1.68 to install and run under SeaMonkey. I got
> permission from NC to release it.
> Links:
> Direct download (until it lands on the xSidebar page):
> On 11/11/12 10:48 am, David E. Ross thus wrote :
>> On 11/11/12 6:52 AM, Lewis Rosenthal wrote:
>>> Hi, guys...
> <snip>
>>> I've just tweaked BP 1.68 to install and run under SeaMonkey. I got
>>> permission from NC to release it.
> <snip>
>> I finally installed BetterPrivacy 1.68 for SeaMonkey, and it continues
>> to operate with SeaMonkey 2.13.2. For this, I had to make two tweaks to
>> the install.rdf file.
>> The first tweak was in the area
>> <!--SeaMonkey-->
>> <Description RDF:about="rdf:#$dLacB4"
>> em:id="{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}"
>> em:minVersion="2.0a1"
>> em:maxVersion="2.6.*"
>> where I changed maxVersion to 2.9.*. Since then, I have not had to
>> update maxVersion because of other changes in how extensions are handled.
>> More important, I had to tweak
>> <!--em:targetApplication RDF:resource="rdf:#$dLacB4"/-->
>> at the bottom of install.rdf. Note that this is commented out and that
>> #$dLacB4 appears both here and in the earlier tweak. By removing the
>> comment brackets (!-- and --) to make
>> <em:targetApplication RDF:resource="rdf:#$dLacB4"/>
>> I was then able to install and use BetterPrivacy 1.68.
>> I believe the commenting of the targetApplication for SeaMonkey was
>> intentional, but I do not know why.
> I've done that in my modified version, and have cleaned up some of the > English in the UI. There's still more to be done, as time permits.
> ;-)
I have installed your version for SeaMonkey 2.13.2 under Windows XP SP3.
I have not observed any problems. However, I normally block Flash with
the FlashBlock extension; so it might be a while before this gets a real
test.
> On 11/11/12 8:38 AM, Lewis Rosenthal wrote:
>> On 11/11/12 10:48 am, David E. Ross thus wrote :
>>> On 11/11/12 6:52 AM, Lewis Rosenthal wrote:
>>>> Hi, guys...
>> <snip>
>>>> I've just tweaked BP 1.68 to install and run under SeaMonkey. I got
>>>> permission from NC to release it.
>> <snip>
>>> I finally installed BetterPrivacy 1.68 for SeaMonkey, and it continues
>>> to operate with SeaMonkey 2.13.2. For this, I had to make two tweaks to
>>> the install.rdf file.
>>> The first tweak was in the area
>>> <!--SeaMonkey-->
>>> <Description RDF:about="rdf:#$dLacB4"
>>> em:id="{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}"
>>> em:minVersion="2.0a1"
>>> em:maxVersion="2.6.*"
>>> where I changed maxVersion to 2.9.*. Since then, I have not had to
>>> update maxVersion because of other changes in how extensions are handled.
>>> More important, I had to tweak
>>> <!--em:targetApplication RDF:resource="rdf:#$dLacB4"/-->
>>> at the bottom of install.rdf. Note that this is commented out and that
>>> #$dLacB4 appears both here and in the earlier tweak. By removing the
>>> comment brackets (!-- and --) to make
>>> <em:targetApplication RDF:resource="rdf:#$dLacB4"/>
>>> I was then able to install and use BetterPrivacy 1.68.
>>> I believe the commenting of the targetApplication for SeaMonkey was
>>> intentional, but I do not know why.
>> I've done that in my modified version, and have cleaned up some of the
>> English in the UI. There's still more to be done, as time permits.
>> ;-)
> I have installed your version for SeaMonkey 2.13.2 under Windows XP SP3.
> I have not observed any problems. However, I normally block Flash with
> the FlashBlock extension; so it might be a while before this gets a real
> test.
Thanks, and I understand that it can take some time. I was actually surprised to see that on the Linux box I used for testing, I actually had a half dozen of those little buggers sitting in there. It's important to note that as the Flash data isn't profile (or browser) specific, even a virgin profile may come up with Flash cookies installed by something else (I guess what surprised me for a moment was that I used a test profile which I know had never hit on a Flash site before, and yet I still had Flash cookies). ;-)
-- Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------
> David,
> I worked well for me when I clicked on the first URL. What web browser did
> you use? I must admit, however, that I ued the latest Firefox web browser
> to do so, and it was on my Android Smartphone that I did this. And once I
> wet to that webpage, I copied the webpage URL, which is:
> https://addons.mozilla.org/en-US/seamonkey/addon/betterprivacy/
> But I was able to get to it. I wonder what error you had and if it had to
> do with your web browser's settings as to why it didn't work becaue the URL
> itself seems to not be faulty, at all. Hope this info helps, hon. :)
David's problem (and indeed, that shared by all of us using SeaMonkey) is that while the original extension will install and function under Firefox, the author decided to stop supporting SeaMonkey, making it more difficult (though obviously not impossible) to install it under anything *other* than Firefox.
Cheers!
-- Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS
Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------
David E. Ross wrote:
>I normally block Flash with the FlashBlock extension
SeaMonkey now includes experimental support for click-to-play, which you might find even better than those add-ons, although some sites confuse it, and there are some issues with outdated plugins in 2.13.2 (which we're hoping to fix in 2.14).
>> But I was able to get to it. I wonder what error you had and if it had to
>> do with your web browser's settings as to why it didn't work becaue the
>> URL
>> itself seems to not be faulty, at all. Hope this info helps, hon. :)
>> David's problem (and indeed, that shared by all of us using SeaMonkey)
> is that while the original extension will install and function under
> Firefox, the author decided to stop supporting SeaMonkey, making it more
> difficult (though obviously not impossible) to install it under anything
> *other* than Firefox.
I noticed that, as well, and didn't know why that author had decided to
stop supporting SeaMonkey.
On Nov 12, 2012 4:40 AM, "Neil" <n...@parkwaycc.co.uk> wrote:
> I normally block Flash with the FlashBlock extension
>> SeaMonkey now includes experimental support for click-to-play, which you
> might find even better than those add-ons, although some sites confuse it,
> and there are some issues with outdated plugins in 2.13.2 (which we're
> hoping to fix in 2.14).
