Slashdot Mirror

Also, when I explained that there's a difference between creating a fix and deploying a fix, I was pointing out that between the time the bug is analyzed and a final fix is deployed will not be as short as some seem to think. If you want to do it properly.

So with there being no mention of the Eudora code base that Qualcomm gave to the Mozilla folks, does this mean there are no plans for those features in Thunderbird? Does Eudora only have implications for the Penelope project?

I think it would be a shame if all we got out of Qualcomm's Eudora are some very superficial changes (new buttons, etc). Then again, maybe I have an overly rosey memory of Eudora and it really didn't have much to contribute.

While I have my little soap-box, how come Thunderbird doesn't start off with a Junk email folder so that I can mark something as Junk and have it go to that folder? Apparently, there are people out there who don't get Junk email!

Are the Qualcomm developers who support Penelope part of this? Will their work be incorporated into Thunderbird, or is it a separate project?

Polishing the current Thunderbird is (at least from the impression I get) actually one of the main goals for Thunderbird 3. It's not all that exciting to talk about, so it only got the "a set of other user interface improvements" line in davida's article, but it's definitely known that making the program just a little bit better in many small ways (my personal pet peeve on this plane is not being able to search across all accounts) would make it hugely more useful for many people, and just good enough for a whole bunch of new potential users.

And no, spinning Mozilla Messaging off actually means it has the chance to finally get the attention it deserves. The Mozilla Corporation has been totally focussed on Firefox (since that's their big cashcow, and it's hard to do two things well), and the Mozilla Foundation is mostly just an oversight and broad planning organization, so a separate organization was needed to let email stand on its own. The Mozilla Foundation hopes that Mozilla Messaging will find its own source of income fairly soon, but they're heavily investing in it right now, and I suspect that if Mozilla Messaging is successful in furthering the goals from the Mozilla Manifesto, but without attracting a lot of income of its own, that funding will just keep on coming (bankrolled by the money Firefox earns). That's pure speculation on my part, and obviously MoFo won't say anything like that, because that would remove much of the incentive for Mozilla Messaging to find its own sources of funding - but it'd make sense.

Mozilla have historically played nice with everybody, including Microsoft.

Right. Because the Mozilla developers are sitting around, working secret. They keep their code all locked up tight and no one can see it. They don't keep a source repository online, updated hourly. They don't publicly discuss the code on any mailing lists or news groups, have a public irc channel where they discuss development, nothing! The Opera developers and everyone else are kept totally in the dark, right up until release! Why, you'd think Mozilla wasn't an open source project, but was instead developed by Microsoft!

Right. Because the Mozilla developers are sitting around, working secret. They keep their code all locked up tight and no one can see it. They don't keep a source repository online, updated hourly. They don't publicly discuss the code on any mailing lists or news groups, have a public irc channel where they discuss development, nothing! The Opera developers and everyone else are kept totally in the dark, right up until release! Why, you'd think Mozilla wasn't an open source project, but was instead developed by Microsoft!

Now, wait a second. If I am developing software package "A", and you develop competing package "B", and I find a hole in A and fix it, then just for laughs test to see if your product has the same hole and then I am kind enough to let you know that it does, then I announce that there is a hole in A, how am I responsible for the security of B at all? I've done you a favor by performing the test and giving you a heads up in the first place! I don't owe you anything.

I'm not sure what you think that has to do with anything. The Mozilla foundation didn't even announce to the public that there was a hole in Opera. The announcement is that there is a hole in Firefox. Why not try reading the advisory? There is NOTHING in there about Opera's susceptibility. You can't even view the bug report without a Mozilla bugzilla account with the proper access - I just logged into my account, and that doesn't include me, so it's not like even the report is generally available. Also, as per the advisory:

These bugs are variations on earlier problems reported by Charles McAuley and Michal Zalewski which were fixed in Firefox 2.0.0.4, as well as an issue reported by hong which was fixed in Firefox 2.0.0.8.

So it seems as though the Opera team has had some warning about problems similar to these in the past - along with the rest of the world.

Could I find and fix a bug in one of my pieces of software in a day? Probably, because all of them are very simple. If I had a development team and a security response team (they do have one of those, don't they?) then I bet "I" could find and fix known security problems in larger software products in a day, too.

Actually, a number of security holes in the Linux kernel have been found, announced, and fixed on the same day, now that I think of it.

Now, wait a second. If I am developing software package "A", and you develop competing package "B", and I find a hole in A and fix it, then just for laughs test to see if your product has the same hole and then I am kind enough to let you know that it does, then I announce that there is a hole in A, how am I responsible for the security of B at all? I've done you a favor by performing the test and giving you a heads up in the first place! I don't owe you anything.

I'm not sure what you think that has to do with anything. The Mozilla foundation didn't even announce to the public that there was a hole in Opera. The announcement is that there is a hole in Firefox. Why not try reading the advisory? There is NOTHING in there about Opera's susceptibility. You can't even view the bug report without a Mozilla bugzilla account with the proper access - I just logged into my account, and that doesn't include me, so it's not like even the report is generally available. Also, as per the advisory:

These bugs are variations on earlier problems reported by Charles McAuley and Michal Zalewski which were fixed in Firefox 2.0.0.4, as well as an issue reported by hong which was fixed in Firefox 2.0.0.8.

So it seems as though the Opera team has had some warning about problems similar to these in the past - along with the rest of the world.

Could I find and fix a bug in one of my pieces of software in a day? Probably, because all of them are very simple. If I had a development team and a security response team (they do have one of those, don't they?) then I bet "I" could find and fix known security problems in larger software products in a day, too.

Actually, a number of security holes in the Linux kernel have been found, announced, and fixed on the same day, now that I think of it.

Seems if they'd kept their whiny mouths shut, nobody would have realised from the vulnerability disclosure that the issue affects Opera. Now EVERYONE knows, from the kiddie scripting 'sploits to the IT manager planning the software deployment for the next few months, who is now seeing why closed-source Opera isn't really such a great choice after all. Even the CVE entry doesn't disclose Opera's vulnerability to this bug. Still, it makes good comedy if nothing else...

I'm suffering from the same problem [stupid web designers who use px instead of em], viewing my pages on a 21" screen at 2048x1536 [which, according to my NVidia X Tool, amounts to 115x118 ppi].

I have found stylish to be very useful. You have to know your way around CSS and the DOM Inspector but you only have to define stuff once for each site you visit and the result is worth it: no more stupid ad columns that eat half my page and a font I can read comfortably w/out needing a magnifying glass.

There are many of us who want text zoom and not page zoom, and it looks like it will be in beta 4.

My extension, NoSquint, will allow nicer integration of page zoom and text zoom features. But for me, it's important I be able to relegate page zoom to second class citizen.

a) no mention of Bacon is made on the cycle collector page.
b) it labels the collector conservative, where Bacon's is accurate.
c) it mentions that your collector might fail to collect a garbage cycle, where by my recollection, Bacon's did not suffer this problem. Are you sure you're using Bacon's cycle collector? Perhaps these are simply the limitations of using C++.
d) why all the different collectors? Why not just use Efficient On-the-Fly Cycle Collection and be done with it? It's not quite as performant as a generational tracing collector, but at least your code won't suffer so many impedance mismatches, and thus be easier to maintain and extend.

If I actually have to tell you what is meant by the term "beta software", well, perhaps you should not be reading /. in the first place. At least send the complaint to http://feedback.mozilla.org/ rather than here.

I've been using Minefield nightlies on Winders for a coupla months now. I cannot recommend it highly enough. Minefield/FF3 is just better than FF2 in every way you can think of - size, speed, UI tweaks (not big UI changes, but lots of little UI tweaks that make things just nicer). Some builds are crappy (as one would expect running HEAD), but I haven't had a really dodgy build in a while. I would go so far as to say: forget this beta, just get the Minefield nightly. ftp://ftp.mozilla.org/pub/firefox/nightly/ is the place to go.

While there are extensions out there that need work to be brought up to speed to work with Firefox 3, a lot of them simply need to have their maxversion updated in the XPI file's install manifest - install.rdf. Obviously, it'd be better for the original developer to do this, but if you don't feel like waiting and aren't afraid of editing a configuration file, you can always do it yourself.

More information can be found here.

And in the provided screenshots, I can already spot ways that the "native" OS X theme doesn't cut it. For example, the screenshot which proudly shows off an Aqua-style select control and button next to a search box also shows those controls using the wrong font and with the text incorrectly placed.

The people creating this theme might not be experts in Mac OS X. Since it looks like you are, you can help. Please file a bug, explaining in detail what needs to be changed.

No, not really. ActionMonkey (the project integrating Tamarin/Spidermonkey as part of Moz2) is not ready yet by a long way. According to the "old" timeline, though, there should be a Firefox 4/Moz2 alpha out in Q2 2008 (though I'm not sure I'd trust any timeline from Mozilla, old or new ;-)

http://wiki.mozilla.org/JavaScript:ActionMonkey
http://wiki.mozilla.org/Mozilla_2

No, not really. ActionMonkey (the project integrating Tamarin/Spidermonkey as part of Moz2) is not ready yet by a long way. According to the "old" timeline, though, there should be a Firefox 4/Moz2 alpha out in Q2 2008 (though I'm not sure I'd trust any timeline from Mozilla, old or new ;-)

http://wiki.mozilla.org/JavaScript:ActionMonkey
http://wiki.mozilla.org/Mozilla_2

firefox breaks if you have the ipv6 module in without an ipv6 capable ISP.

the party lines seems to be that a number of serious gating ipv6 bugs cannot be marked as gating because no devs can verify them, for lack of ipv6 setups to test. a highly suggest <a href="https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&content=ipv6">looking at the ipv6</a> bugs if you're bored at work and want cause for a good chuckle.

i've always been an opera proponent because firefox consumes far more resources than is concievably acceptable for any piece of code to use (my p1120 laptop IS perfect, no theres nothing wrong with 224mb of ram and an 800mhz crusoe), but the mishandling of critical showstopping issues in firefox 3 has been hilarious. firefox 3 has made enormous strides to try and become something like respectable, but ten percent of linux users are going to have firefox fall flat on its face and thats <i>hilarious</i>.

I've been using Firefox 3 (trunk builds) before Firefox 2 was an official release. I love it.

Whatever happened to:

> Issue one major release every year (Fx 3 in 2007, Fx 4 in 2008, etc.) since it helps drive upgrades and adoption

http://wiki.mozilla.org/Firefox3/Firefox_Requirements#Release_Roadmap

Now my dream is to see a QT brand of Firefox again, perhaps using QT 4's built-in Webkit. Unify Konqueror, Safari and Firefox on one rendering engine and work towards making that the best damned rendering engine out there. They spent nearly two years on the new Gecko rendering engine, and it still isn't as fast as Webkit/KHTML. Firefox has all the features I want for the most part. I'm not saying they should abandon GTK, but they support multiple widgets and toolkits. Someone please give me a QT 4 branch of Firefox and I've be very happy.

Although if you have a mac, be sure to install the proto theme. Although if you have a mac, you also should try the latest Webkit build too. Its ridiculously fast.

That is all.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

• Memory leaks
  • 333078 - XPCOM Cycle Collector. (Cycle collection has similar goals to tracing garbage collection but integrates better with reference counting. Turning on cycle collection fixed entire classes of leaks, both in Firefox and in extensions.)
  • 330128 - Calling cancel() on a timer doesn't drop reference to callback.
  • Many more: 331 bugs fixed on trunk with the "mlk" keyword.
• Code size and memory use
  • 296818 - Don't hold onto decoded image data for so long.
  • 143046 - Reduce memory use for animated GIFs by storing frames other than the first at the original 8 bits.
  • Take a string constructor out of line. (From 345517.) (1% code size win.)
  • 332174 - Drop SOAP support. (2% code size win.)
  • 313309 - Provide table-driven QI mechanism.
  • 407459 - [Windows] Switch from default MSVC malloc to jemalloc for better memory allocation speed and lower fragmentation.
  • Many more: 100 bugs fixed on trunk with the "footprint" keyword.

X64 is compatible with x86. Is there some issue I'm not aware of?

You mean like Mozilla? I'm not sure if private security mailing lists, "confidential bugs" and all that are reprehensible, but they might be. Or do you mean another type of "reprehensible"?

Their existence may be repulsive

You mean like Mozilla, or do you mean another type of "repulsive"?

My patience for these parasites is exhausted.

Indeed.

You mean like Mozilla? I'm not sure if private security mailing lists, "confidential bugs" and all that are reprehensible, but they might be. Or do you mean another type of "reprehensible"?

Their existence may be repulsive

You mean like Mozilla, or do you mean another type of "repulsive"?

My patience for these parasites is exhausted.

Indeed.

Aren't Firefox plugins just Javascript?

As I understand it, that's one of the major reasons that Firefox can get bogged down.

Or you could use the incredibly good PasswordHasher extension.

Try the Secure Login Add-on, it just might be what you are looking for.

https://addons.mozilla.org/en-US/firefox/addon/4429

I really like this one: https://addons.mozilla.org/en-US/firefox/addon/3282 (Password Hasher)

gre is constant data. This report is FUD.

Firefox is open source; anyone who wants to view view-source:resource:///greprefs/all.js can just as easily load http://mxr.mozilla.org/mozilla1.8/source/modules/libpref/src/init/all.js?raw=1 it has the same content.

all.js is *not* user data, it's *public* app data. Your preferences are stored in prefs.js which are not exposed by greprefs.

Do you have a better way to store all your passwords?

Try Secure Login.

the page layout (right vs left) is hardly a major issue when it concerns Foxit, a PDF -reader-. I can fully understand if you want it to work correctly for a PDF authoring app, so that it comes out the printer the way you see it on screen, but geeze.

It's like calling ThunderBird "beyond hope" because the thunderbird team appear to be unwilling to fix the folder rename issue on the Windows platform (renaming "Test" to "test" will tell you that it already exists. durrr. https://bugzilla.mozilla.org/show_bug.cgi?id=92165 - July 2001. )

That said, next version (there's always a next version) of Foxit should have this implemented a la Adobe's Reader. If it is, then that's implemented a whole lot quicker than the aforementioned asinine TB bug ( http://www.foxitsoftware.com/bbs/archive/index.php/t-192.html - September 2005 ), although I agree that it should have been implemented in an afternoon's work (even done dirtily so by inserting a blank invisible page in the page array).

You can get it here: https://addons.mozilla.org/en-US/firefox/addon/59. Under Tools->User Agent Switcher you can choose between several user agents that you want FF to report. Very handy for sites like these.

Strange. I don't know why, but this STEP reminds me of BASIC. :-)
Is this supposed to be a step forward?

Wikipedia page for ISO STEP mentions that many consider replacing it with XML, or rather creating XML schemas to represent the information STEP does (I didn't find Wikipedia's external reference for this though).

It's not true that XML cannot be rendered incrementally. This Mozilla FAQ points out that versions before Firefox 3/Gecko 1.9 don't support it, which makes me believe that Firefox 3 does support it (I didn't check it myself).

The fact that XML allows you to check it for validity when you have the whole document doesn't prevent you from processing the parts you read already. SAX based parsers work that way, by passing events whenever one element is complete, you don't have to wait for all the document to finish to process the snippet at hand. If the document isn't valid, the processing will stop at the point where the error was found.

F-Spot will export to Picasaweb, Flickr and others. Also there is an addon for Firefox called Firefox Universal Uploader that will do the same function for many sites.

As a matter of fact, I emailed them about this very problem last November. Their response was that "folks were copying the text of our articles and circulating them in e-mail, despite our copyright notices and even our asking them to stop." I will concur that not being able to even select text is extremely annoying, along the lines of a dialog saying "Copyright 1992" when you right-click. Unless, of course, you've got NoScript.

I won't mess with your revenue model if you won't serve pr0n ads or hide sneaky code, 'k?

Oh, so I guess nobody else's shit stinks, right?