You say you've tried mod_deflate.
Why not using mod_gzip instead of mod_deflate? I don't think i've seen any major problem report for mod_gzip useage... (yet?)
Yes, right, because virii (no not viruses) don't exploit security holes to propagate now do they.
I mean, it's well known that virii propagate through magical warpholes (pink and pastel blue, with silver stars all around)(and open it by dancing a bit and singing "Lunar Prism, Make Up") and just pop on your HD from thin air.
Btw, FireFox didn't invent Gecko... It's just a browser on TOP of Gecko
Right, and Gecko is?
Oh yeah, the rendering engine of the Mozilla foundation, built nearly from scratch from the charred remains of Netscape code (most was dumped, labelled as unusable trash at the start of the Mozilla project).
Gecko is the rendering engine, Mozilla and Firefox are the useable products/interfaces to Gecko, as are K-Meleon (lightweight Win32-based Gecko browser) or Camino (native MacOS Gecko-based browser)
Gecko and Firefox' fates are deeply intertwined, even more so since the Foundation dropped Mozilla Seamonkey, and if you check the Firefox roadmap you'll notice the slight coupling between Firefox and Gecko.
Saying that Firefox is "just a browser on top of gecko" is as stupid as saying "Safari is just a browser on top of Webcore".
I don't know why anyone informed would say this. The CSS in IE6 is kinda bad, but it's clearly supposed to be W3C CSS and not something proprietary.
1- It's not "supposed to be the W3C CSS", of the few properties that are implemented (CSS1, CSS2 is barely scratched) many are wrongly implemented [box model, only fixed in Strict mode IE6] and half the implementation is heavily bug ridden
2- You probably missed all the proprietary MS crap in their implementation of the CSS, such as scollbar shit, that was NOT implemented in a W3C-compliant style (W3C allows proprietary CSS properties, but you HAVE to use precise prefix of type "-name-", which is why you see such things as -moz-outline)
3- CSS in IE6 is not "kinda bad", it's an awful heap of crap and a pain to work with from a dev's point of view
4- And if we extend from W3C's CSS to W3C's everything, MSIE sucks at W3C's HTML (heaps of missing tags, or not completely implemented ones), XHTML (which it doesn't understand at all in fact), W3C DOM/DOM Events and their binding in ECMA-262 (also known as ECMAScript/Javascript), XSL/XSLT...
Now I think back to 1995, when IE focused on user needs over software perfection and the following of published specifications. And look what a mess of incompatibility we have today of javascript, css, java VMs, etc. Mainly because M$ focused on 'the needs of users.' No thanks, I'll stick to the specs.
No they didn't, they focused on "How to throw Netscape out of the browser market, and quite soon if you please", they never gave a damn about the customer.
Let's check why it disabled your extensions:
Most of the current extension state that they are coded for Firefox 1.0 (or Firefox 0.9 to 1.0, more rarely 0.7 to 1.0).
Trunk builds (aka nightlies) are NOT Firefox 1.0, they're "soon to become" Firefox 1.1.
Extensions are therefore not allowed to run them because the extensions themselves state that they shouldn't run on FF 1.1.
You can go and edit your extensions files:
Go to your profile folder (under windows it's %APPDATA%\Mozilla\Firefox\Profiles\randomgibberish.username)
Go to the "extensions" folder
Open the "Extensions.rdf" file in a text editor (notepad is ok, things like SciTE or UltraEdit work better though)
Now check all those little "em:maxVersion" thingies, there is at least one for each extension (often more, when the exetension is also Mozilla and Thunderbird compatible)
Bump the maxVersion to "1.1" everytime it says "1.0" or "1.0+"
Save
Restart firefox
Does work like a charm for releases (but may break your browser if an extension was REALLY broken by the update, you're doing that at your own risk mate), does probably work with nightlies too, just find out what version they identify themselves as.
They're not fixed indeed, current nightlies are "images" of the soon to become 1.1 which should be due by June (or July if the devs are as horribly behind schedule as they seem to be)
I *really* hope you were joking when you wrote that down, because it's one of the most beautiful pieces of bullshit i've read today...
Please do pay a visit to the CSS Zen Garden and compare IE renderings to FF renderings.
the Special Effects Designs are the most interresting ones in terms of IE sucking badly, BTW...
It should be noted that 1.0.4 also features a JS bugfix which hastes said JS execution by around 20%.
May sound like it suck... if you don't know that the whole XUL thing (basically everything in firefox but the Gecko engine itself: interface, extensions, userscripts,...) is pure Javascript.
Actually, had you really followed the story that bug had been discovered less than a week before being disclosed by a third party.
The bug was discovered and filled in Bugzilla by the discoverer
It was kept hidden while the Foundation was working on a fix (quite common for grave security issues)
a few days later (5? i think?) a third party (not the discoverer, not the foundation) fully disclosed the bug to the public
And the Foundation now releases the fix.
The bug has NOT "sit" for months in BZ, and the discoverer, being a member of the Full Disclosure list, wouldn't have allowed it anyway.
Mind you, I'm not suggesting that the system isn't currently broken; rather simply that not enough shit has hit the fan yet for people to be forced into caring.
The problem is that given the current "pain threshold" (sp?) of the western populations, we'll need quite a lot of shit and it'll probably break the fan when it'll hit...
ts the old adage where you don't really care why your neighbours are being arrested until they come for you. Same principle. Enough people are enjoying worry free lives (save for the material worry we create to substitute for real worries such as where is my next meal coming from) such that we just havn't hit a critical mass of folks who think we need a substantial change.
Feingold and the rest are driven by "opposite of Bush" regardless of the content.
And this is true not only in the US, but in great many western countries (replace "opposite of bush" by "opposite of whatever party currently holds the power")
Most modern westerner politicians are so childish and have such stupid ways of setting their opinions it's quite scary they're the ones with the power...
And there are so damn few alternatives...
It's pretty much been confirmed that there was damn little intelligence left in a good many Western nations' intelligence agencies.
You'd be much closer to the truth if you were able to edit "a good many western nations'" to "the USA's", because that's the one that has been confirmed
Which is why it's usually possible to "claim" a bounty: other people will know it's claimed and will only work on it at their own risk (the one of being second, and the one of being hated by the initial claimer)
1- Yes I do know
2- No, mp3 encoding has very specific losses and artifacts on quite a lot of frequencies of the spectrum (do visit the HydrogenAudio forums for more informations) and doesn't even remotely compare to lossless even with very high bitrate (said bitrates yielding higher data sizes than good lossless codecs BTW)
3- Recompression from lossy mp3 to any other lossy format yields artifacts and data loss exponentially higher than the artifacts and data loss of any of the two lossy codecs
MP3, even at high bitrates, is nowhere near CD quality or lossless quality, which is in itself quite far from the "theorical analogic" quality (said theorical analogic being when not taking in account aging and physical artifacts of LPs, since it's the most common analogic music medium)
a) Who said anything about "free"? I'd be happy to _buy_ MP3s
You shouldn't. Being happy to buy FLAC/MonkeyAudio (lossless compression) files I can understand, gladly buying mp3 files I have trouble understanding, especially with the kind of "deals" you get right now, with mp3/wma files being the same price as the CD track... only with lower quality and less flexibility
Best spell checkers are supposed to include a grammar checker as well.
It's one of the few MSWord features that still aren't mirrored in OOo, and even though grammar checkers are much harder to create than spell checkers, I found Word 2003's to be quite nice and work quite well (the green wavy thing is butt ugly though)(and I don't mean "nice lil 19yo chick's butt ugly" but "55yo 250 pounds greasy hairy male's butt ugly")
Slashdot Mirror
You say you've tried mod_deflate.
Why not using mod_gzip instead of mod_deflate? I don't think i've seen any major problem report for mod_gzip useage... (yet?)
Yes, right, because virii (no not viruses) don't exploit security holes to propagate now do they.
I mean, it's well known that virii propagate through magical warpholes (pink and pastel blue, with silver stars all around)(and open it by dancing a bit and singing "Lunar Prism, Make Up") and just pop on your HD from thin air.
You can get a DA surviving, the only requirement is removing your genetic data from the Gene Pool, aka not being able to reproduce.
If the toxics got his balls he's in, if they didn't he'll only get (as you mention it) a Honorable mention.
Oh yeah, the rendering engine of the Mozilla foundation, built nearly from scratch from the charred remains of Netscape code (most was dumped, labelled as unusable trash at the start of the Mozilla project).
Gecko is the rendering engine, Mozilla and Firefox are the useable products/interfaces to Gecko, as are K-Meleon (lightweight Win32-based Gecko browser) or Camino (native MacOS Gecko-based browser)
Gecko and Firefox' fates are deeply intertwined, even more so since the Foundation dropped Mozilla Seamonkey, and if you check the Firefox roadmap you'll notice the slight coupling between Firefox and Gecko.
Saying that Firefox is "just a browser on top of gecko" is as stupid as saying "Safari is just a browser on top of Webcore".
Which is why they don't intend to release any patch for the aforementioned bug...
Do they?
2- You probably missed all the proprietary MS crap in their implementation of the CSS, such as scollbar shit, that was NOT implemented in a W3C-compliant style (W3C allows proprietary CSS properties, but you HAVE to use precise prefix of type "-name-", which is why you see such things as -moz-outline)
3- CSS in IE6 is not "kinda bad", it's an awful heap of crap and a pain to work with from a dev's point of view
4- And if we extend from W3C's CSS to W3C's everything, MSIE sucks at W3C's HTML (heaps of missing tags, or not completely implemented ones), XHTML (which it doesn't understand at all in fact), W3C DOM/DOM Events and their binding in ECMA-262 (also known as ECMAScript/Javascript), XSL/XSLT...
virtual insightful mod for parent, that kid should've been shot for trying to do something THAT stupid.
At least we now know the name of one next year's nominees to the Darwin Awards
Most of the current extension state that they are coded for Firefox 1.0 (or Firefox 0.9 to 1.0, more rarely 0.7 to 1.0).
Trunk builds (aka nightlies) are NOT Firefox 1.0, they're "soon to become" Firefox 1.1.
Extensions are therefore not allowed to run them because the extensions themselves state that they shouldn't run on FF 1.1.
You can go and edit your extensions files:
- Go to your profile folder (under windows it's %APPDATA%\Mozilla\Firefox\Profiles\randomgibberis
h .username)
- Go to the "extensions" folder
- Open the "Extensions.rdf" file in a text editor (notepad is ok, things like SciTE or UltraEdit work better though)
- Now check all those little "em:maxVersion" thingies, there is at least one for each extension (often more, when the exetension is also Mozilla and Thunderbird compatible)
- Bump the maxVersion to "1.1" everytime it says "1.0" or "1.0+"
- Save
- Restart firefox
Does work like a charm for releases (but may break your browser if an extension was REALLY broken by the update, you're doing that at your own risk mate), does probably work with nightlies too, just find out what version they identify themselves as.They're not fixed indeed, current nightlies are "images" of the soon to become 1.1 which should be due by June (or July if the devs are as horribly behind schedule as they seem to be)
Since Mac is now officially Unix you can manage to buy and install a *real* mouse on an Apple box, and get more than one working button too !
Please do pay a visit to the CSS Zen Garden and compare IE renderings to FF renderings.
the Special Effects Designs are the most interresting ones in terms of IE sucking badly, BTW...
It should be noted that 1.0.4 also features a JS bugfix which hastes said JS execution by around 20%.
...) is pure Javascript.
May sound like it suck... if you don't know that the whole XUL thing (basically everything in firefox but the Gecko engine itself: interface, extensions, userscripts,
Actually, had you really followed the story that bug had been discovered less than a week before being disclosed by a third party.
The bug was discovered and filled in Bugzilla by the discoverer
It was kept hidden while the Foundation was working on a fix (quite common for grave security issues)
a few days later (5? i think?) a third party (not the discoverer, not the foundation) fully disclosed the bug to the public
And the Foundation now releases the fix.
The bug has NOT "sit" for months in BZ, and the discoverer, being a member of the Full Disclosure list, wouldn't have allowed it anyway.
I haven't had to reinstall an extension for a long time.
Didn't you know that the "Check for updates" works for extensions?
Most modern westerner politicians are so childish and have such stupid ways of setting their opinions it's quite scary they're the ones with the power...
And there are so damn few alternatives...
This doesn't mean that his offer is a Bad Thing ©, just that he obviously balanced risk vs reward...
Which is why it's usually possible to "claim" a bounty: other people will know it's claimed and will only work on it at their own risk (the one of being second, and the one of being hated by the initial claimer)
Mod parent insightful please.
OSS bounties are not supposed to feed you, they're supposed to be a gift-reward for your "free" work on OSS projects.
wxWidgets has had "open bounties" (anyone can set a bounty for a feature or an implementation) for quite a long time now BTW
1- Yes I do know
2- No, mp3 encoding has very specific losses and artifacts on quite a lot of frequencies of the spectrum (do visit the HydrogenAudio forums for more informations) and doesn't even remotely compare to lossless even with very high bitrate (said bitrates yielding higher data sizes than good lossless codecs BTW)
3- Recompression from lossy mp3 to any other lossy format yields artifacts and data loss exponentially higher than the artifacts and data loss of any of the two lossy codecs
MP3, even at high bitrates, is nowhere near CD quality or lossless quality, which is in itself quite far from the "theorical analogic" quality (said theorical analogic being when not taking in account aging and physical artifacts of LPs, since it's the most common analogic music medium)
Best spell checkers are supposed to include a grammar checker as well.
It's one of the few MSWord features that still aren't mirrored in OOo, and even though grammar checkers are much harder to create than spell checkers, I found Word 2003's to be quite nice and work quite well (the green wavy thing is butt ugly though)(and I don't mean "nice lil 19yo chick's butt ugly" but "55yo 250 pounds greasy hairy male's butt ugly")