Slashdot Mirror
Firefox 2 To Have Anti-Phishing Technology
Mitchell Bronze writes "Mozilla's Mike Shaver said in an interview that the upcoming Firefox 2 will have anti-phishing capability using technology that might come from Google." From the article: "With the continued rise in online attacks, security tools have become something Web browser makers can use to try to stand out. Microsoft plans to include features to protect Web surfers against online scams in Internet Explorer 7, due later in 2006. Similar functionality is already in Netscape 8 and Opera 8, both released last year. 'It is another example of the energy that has returned to the browser market,' Shaver said."
Yup, Firefox 2 everyone... With as long as it took me to see a complete FireFox "1", you can expect phishing to be completely phased out by the time you see the second incarnation.
Hell, by then they'll just hack your brain directly... oh gn0~!!
I'm still looking for the Anti-Memory-Leak technology. Maybe the Firefox devs should get off their asses and fix their bloated POS browser.
I want my ability to render whatever site I want, even typoed URLs leading to a knock-off of bankofamerica hosted in Russia. No IFs and BUTs.
that cache is only part of the problem, no matter what the monkeys at mozilla says.
disabling the caching (in about:config) doesn't solve the problem. just yesterday i had firefox with 1 tab consumming 350 megs of memory.
don't be misled by the coders, firefox is still leaking like a bottomless bucket
If I remember correctly, it's something to do with cacheing the pages. Firefox caches something like 25 previous pages you've been to... on each tab.
Yeah, the liars at Mozilla did indeed say this, but they're lieing. The truth it that Firefox leaks memory at a truely alarming rate, along with using a crappy custom allocator that loses all the benefits of the highly optimized allocator that most C runtimes come with. ("Let's see, this problem has already been solved a million times before, and almost all C runtime libraries attempt to create a well-optimized allocator, why don't we create our own allocator anyway?")
The truth is this. Firefox caches the last 2/4/8 pages if you have 256/512/1024MB of memory. That's IT. Each page SHOULD take up 4MB of memory MAX. That people are seeing an extra 100-200MB (up to 500MB in extreme cases) are simply due to MEMORY LEAKS that Firefox has.
The people claiming that the memory leak is due to a "feature" are simply trying to distract people from the real giant memory leaks and general flakeyness that the browser has. Firefox - well, technically, Mozilla/Gecko, it's not really Ben Goodger's fault - is a poorly designed piece of crap. That's why there are memory leaks. That's why it crashes.
It's NOT a feature, no matter how many times they LIE and say it is. It's a REAL BUG. The arrogance in naming bugs "features" is something we frequently like to blame Microsoft for doing, but the Mozilla developers are FAR more guilty of it than Microsoft has ever been. (Read some random bug reports on their Bugzilla. It's quite enlightening.)