Slashdot Mirror

and TFA has a Flash ad...

So well written that they couldn't port it to 64bit platforms without rewriting the underlying script host from the ground up.

That's some "Real Quality Software" right there and it's great that flash is so instrumental in furthering the promise of an open, accessible web. How I wish every web page was a chunk of executable bytecode.

Once again NoScript helps out here since it can block Flash. I don't run Flash on any pages that don't absolutely require it, and I find few that do. Flashblock is another option for Firefox users that only want to block Flash and nothing else. Browse safely everyone.

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

That's doable for Firefox as well:

http://wiki.mozilla.org/Firefox:2.0_Institutional_ Deployment

and inparticular:

http://homepages.ed.ac.uk/mcs/FirefoxADM/Readme.ht m

IE Tab

"We would still be thankful for RMS though. "

Thank you, Richard!

Thank you, Richard!

Thank you, Richard!

Thank you, Richard!

Thank you, Richard!

Thank you, Richard!

Thank you, Richard!

Thank you, Richard! And happy birthday!

That's why we have IE Tab. https://addons.mozilla.org/en-US/firefox/addon/141 9

This already exists and is called repagination . It is not perfect, in that it essentially concatenates the pages together rather than expanding the single content block, but it is better than continual clicking between pages. Overall an excellent extension.

To remove the ads, just use AdblockPlus with one of the subscriptions, for zero effort expended ad blocking.

This already exists and is called repagination . It is not perfect, in that it essentially concatenates the pages together rather than expanding the single content block, but it is better than continual clicking between pages. Overall an excellent extension.

To remove the ads, just use AdblockPlus with one of the subscriptions, for zero effort expended ad blocking.

WMP and iTunes both run fine under Linux actually.

Reality check. Go to the Apple iTunes download page.. Note the available options: "Windows 2000, XP, or Vista", or "Mac OS X". Yes, there are people who have been able to get iTunes to run on a Mac under some emulator. And there have been attempts at an iTunes clone. But Apple put a stop to that.

As for Windows Media Player, even for Firefox, it doesn't work on Linux. Linux support is listed as "unavailable". Some programs can play some formats of .AVI files on Linux, but not the ones that require codec or DRM downloads from Microsoft servers.

And how will they compete with Free software anti-virus?

pardon my ignorance, but what are these google ads?

Firefox is licensed under GPL 2.0 or later and LGPL 2.1 or later, as well as a couple of other licenses.

They would be scared of their own shadow, then. There is a plenty of space in the OS based market as the proprietary, legally.

Why not use both? I have my Sunbird (Lightning, actually) syncing back and forth with Google Calendar so I get a real desktop client at home, but still can see my schedule online from anywhere.

It's mentioned in the release notes, and you can get the extension here.

Why not use both? I have my Sunbird (Lightning, actually) syncing back and forth with Google Calendar so I get a real desktop client at home, but still can see my schedule online from anywhere.

It's mentioned in the release notes, and you can get the extension here.

Should have looked before I posted. Bidirectional access to Google Calendar from Sunbird is possible with the Provider for Google Calendar extension...

Lightning is the Thunderbird extension that provides the same capabilities as Sunbird. It supports iMIP and other email invitation formats. It also has a Provider for Google Calendar Extension .

Lightning is the Thunderbird extension that provides the same capabilities as Sunbird. It supports iMIP and other email invitation formats. It also has a Provider for Google Calendar Extension .

Maybe we could call it SeaMonkey or something... Hmm...

http://www.mozilla.org/projects/seamonkey/

I know you know this exists, but it's polite to include a URL when you're sassing someone who doesn't. ;)

Screenshots here: http://www.mozilla.org/projects/calendar/sunbird/s creenshot.html

While it's true that it's much better to follow the RFC here, just switching to POST doesn't solve the CSRF problem. An attacker could set up a malicious Web page which has a form with all the necessary parameters and a JavaScript to automatically submit it, hence meeting the POST requirement. Similarly, if the client has an older version of Flash or a buggy version which does not obey same-source security principles, the attacker could embed a malicious SWF which creates the entire HTTP request from scratch, even forging the Referer header if you were checking that as a security measure.

This is another good reason for using Firefox extensions such as Flashblock and Noscript. As a client, you can protect yourself pretty easily from a lot of these attacks. Noscript also has some nice features which help filter out the more common brands of XSS attacks.

A lot of open source advocates are pretty put off by closed source hardware drivers but a hard disk search utility, eww. I think this is going be be about as popular as another SCO Linux distribution would be.

I wonder how long it will take for an open source version to develop, that not only looks better, and does a better job, and is guaranteed free from advertising for life but also when it does phone home it only ever phones you.

With regards to privacy, fot Internet search I have started using this, https://addons.mozilla.org/en-US/firefox/addon/317 3, not sure whether it's doing and good but I hope it confuses the crap out of all those targeted advertising schemes. I would think if enough people started to use it, it would also end up averaging out the search engine hit statistics, but luck for google's apparent market share.

apparently when I signed up for the University of Michigan testing stuff it clobbered my account profile with whatever was going on at the time and now none of this "discussion2" stuff works

NoScript does that on Firefox, I'm sure there's something equivalent on most other browsers worth their own salt and also on IE.

You're actually better off using CookieSafe (or similar) to handle cookies. Other than that you are at least :) 100% on the mark.

Try this Firefox plug-in. Never look at eBay's stupid ads again:

https://addons.mozilla.org/en-US/firefox/search?q= customizegoogle&status=4
http://www.customizegoogle.com/

Most Significantly, perhaps is:
Firefox 3.0 Alpha 5 (Gran Paradiso)

From the 43 selectors 32 have passed, 4 are buggy and 7 are unsupported (Passed 369 out of 578 tests)

Get Firefox 3.0 Alpha 5 here: Mozilla's Public FTP

Yes, it is technically alpha software, although it is no less reliable than Firefox 2.0, from what I have found.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

A few years ago, I wanted Mozilla to be able to play a sound when a download completes. I got on IRC and asked for help, and a couple very patient developers helped me understand where the code was that needed to be patched, and how to fix the issue. As I found other things that were missing, or things I didn't like, I wrote more and more patches, each time with less help - probably 99% of the lines of code in my early patches were written over IRC by more experienced devs, and pasted into a text editor by me :-).

I started taking on code-cleanup-type bugs, and eventually, as I became more familiar with the codebase, more visible bugs (and even ones that didn't affect me personally). I've fixed quite a few bugs now, and have quite a bit of responsibility.

I don't know how well it'll go if you don't have a vested interest in your contributions - it's incredibly difficult to get into a huge codebase like Mozilla. I had written programs of up to a few thousand lines of code before, but working in a multi-million-line project is very different. Start with small changes, and don't feel bad when your patches have to go through many revisions before being accepted.

With Mozilla, you might want to look at good first bugs for things that might be easier for someone just starting. As the sibling says though, you want to build first (which can be a challenge in itself in the Mozilla case, sadly).

Mozilla-specific again - you might want to consider starting by writing an extension. Helps you learn the same things, but no build system hurdle and no need to wait for somebody for reviews before end-users can see it.

And if you can't find anything you actually *want* to do, why, then you can't do better than get some good experience on the wonderful Mozilla projects! Head over to https://bugzilla.mozilla.org/, pick an interesting open bug, and go to it!

With Mozilla, or many other large projects, it's a better idea to go look at the build instructions, and once you can understand and follow them and get a working executable out, THEN try messing with the code. Mozilla projects can be very difficult to get compiled (there are lengthy guides on the subject) and being able to actually test your code is an important first step.

Or some other type of abstract class of programming task. Writing documentation is also a good way to learn - there's always a need for good docs, and you have to get to know the software really well to write them.

Pull the current source. Take a poke around. Grep for comments. Look at the changelogs. Look at what's being worked on, where the problems are, how much activity is going on, how many contributors there have been. Scratch your itch!

And if you can't find anything you actually *want* to do, why, then you can't do better than get some good experience on the wonderful Mozilla projects! Head over to https://bugzilla.mozilla.org/, pick an interesting open bug, and go to it!

Good luck, and have the appropriate amount of fun :)

Or some other type of abstract class of programming task. Writing documentation is also a good way to learn - there's always a need for good docs, and you have to get to know the software really well to write them.

Pull the current source. Take a poke around. Grep for comments. Look at the changelogs. Look at what's being worked on, where the problems are, how much activity is going on, how many contributors there have been. Scratch your itch!

And if you can't find anything you actually *want* to do, why, then you can't do better than get some good experience on the wonderful Mozilla projects! Head over to https://bugzilla.mozilla.org/, pick an interesting open bug, and go to it!

Good luck, and have the appropriate amount of fun :)

LeetKey FF extension. Use it to keep your email privacy. Before sending a message, select it, right click on it, select 'LeetKey, Text Encryptors, AES Encrypt' menu option and type in a password. Tell the other party to use AES Decrypt and tell them the password for this email.

I just did a quick bit of research and found that while iCal and Mozilla Calendar share the same file format, iCal still doesn't share calendars over webDAV or FTP, which will be a stumbling block for collaborative use, so while Google Calendar wants to keep its users in the browser, the technology isn't quite there for a genuinely open collaborative calendar. I went through this a few months ago when planning a holiday with a friend in Taiwan - we ended up planning on a shared Google calendar, which I then exported to iCal and then synced to my Nokia E61. Anything to avoid using pen and paper...

1. More elegant UI (I admit, this is mostly preference. Firefox isn't bad, and *much* better on Windows at this point. Safari needs a lot of UI work on Windows.)

3. Close buttons for each tab in each tab (yes, I know Firefox finally got on board with this in v2.0)

4. Integrates with Apple's Keychain, so I only have to set up my encryption certificates once for both Mail.app and Safari.

5. Safari is better at resuming stalled downloads.

6. Private Browsing.

7. iSync support for syncing bookmarks across multiple Macs.

1. More elegant UI (I admit, this is mostly preference. Firefox isn't bad, and *much* better on Windows at this point. Safari needs a lot of UI work on Windows.)

3. Close buttons for each tab in each tab (yes, I know Firefox finally got on board with this in v2.0)

4. Integrates with Apple's Keychain, so I only have to set up my encryption certificates once for both Mail.app and Safari.

5. Safari is better at resuming stalled downloads.

6. Private Browsing.

7. iSync support for syncing bookmarks across multiple Macs.

1. More elegant UI (I admit, this is mostly preference. Firefox isn't bad, and *much* better on Windows at this point. Safari needs a lot of UI work on Windows.)

3. Close buttons for each tab in each tab (yes, I know Firefox finally got on board with this in v2.0)

4. Integrates with Apple's Keychain, so I only have to set up my encryption certificates once for both Mail.app and Safari.

5. Safari is better at resuming stalled downloads.

6. Private Browsing.

7. iSync support for syncing bookmarks across multiple Macs.

1. More elegant UI (I admit, this is mostly preference. Firefox isn't bad, and *much* better on Windows at this point. Safari needs a lot of UI work on Windows.)

3. Close buttons for each tab in each tab (yes, I know Firefox finally got on board with this in v2.0)

4. Integrates with Apple's Keychain, so I only have to set up my encryption certificates once for both Mail.app and Safari.

5. Safari is better at resuming stalled downloads.

6. Private Browsing.

7. iSync support for syncing bookmarks across multiple Macs.

1. More elegant UI (I admit, this is mostly preference. Firefox isn't bad, and *much* better on Windows at this point. Safari needs a lot of UI work on Windows.)

3. Close buttons for each tab in each tab (yes, I know Firefox finally got on board with this in v2.0)

4. Integrates with Apple's Keychain, so I only have to set up my encryption certificates once for both Mail.app and Safari.

5. Safari is better at resuming stalled downloads.

6. Private Browsing.

7. iSync support for syncing bookmarks across multiple Macs.

How is this insightful? Firefox has been working on Acid2 compliance for a while now.. it required some big changes to gecko, so they told us it wouldn't happen until FF3.

Go here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nig htly/latest-trunk/

Download the Firefox 3.0 Alpha (which is far more stable than Safari 3 beta), and check for yourself.. passes Acid2 with flying colors.

If they really want the market share, make Firefox 3 worth going back to, and I, for one, will start using FF again.

RTFA. They don't want the market share. They want to keep the web open, as stated in the Mozilla Manifesto.

Anyway, they do have the market share. Apple releasing Safari for Windows will increase consumer choice and the competition will help all browsers improve. It will also help web developers realize they can't develop for only one or two browsers, but instead should develop according to standards unless they want to turn away significant fractions of visitors. I see only good coming out of the release, regardless of what Jobs' intentions are.

Their estimate is 1% of the smartphone market in the first year. You dictate nothing at one percent. Even pretending that it will be as popular as the iPod (by ignoring the millions of smartphones, and billions of feature phones already out there), the carrier lock-in will still put a hard upper bound on its acceptance. If I thought they'd have even 5% in two years, I'd put my savings in Apple stock, but I still wouldn't bother caring about the iPhone as a unique platform.

In three years, Microsoft will have the mobile IE be as functional as the desktop, Minimo won't be the bloated pig it is now, Opera and Nokia's browser will still be best browsers you've never used, and there will undoubtedly be open source newcomers based on the improvements to KHTML.

So I'd bet on c.) mobile browsing looks just like it does now, only sucks less.

Just wait till FF 3.0, it will probably support 10.3.9 and up
http://wiki.mozilla.org/Firefox3/Firefox_Requireme nts#Platform_Support
Still better than Safari 3 support but at least they have a good excuse. Safari 3 uses a lot of the new framework changes in OS X Leopard which make backwards compatibility very hard.