Deer Park logo is better


The Mozilla Foundation has released the first alpha release of what will become Firefox 1.1. To prevent confusion of Firefox 1.0.x users, they have gone to great lengths to make sure only developers and testers download it. Among them are calling the release by its codename (Deer Park), changing the product name for the developer release, and even changing the icon. Instead of the Firefox “humping a globe“, it’s just a globe. Kind of apropos, seeing as it isn’t a finished product.

Very soon after installing Deer Park builds, I found that I prefer the Deer Park logo.
Here are some comparison shots:

Firefox 1.0.x Deer Park

I prefer the Deer Park logo because:

– it is more simple. That image is easier to remember, and easier to redraw.

– I can’t think of a better symbol for a web browser than a globe. A always loved how the old Netscape throbber inspired my imagination about what could be done with the product and the technology. The Firefox icon contains more fox than globe.

The Mozilla Foundation has an animal theme going, which is good for identity and association of all Mozilla products, but the Firefox icon doesn’t really communicate what the product does.
I prefer the globe.

Netscape 8 is now secure…at least when using gecko

Back when the Beta version of Netscape 8 was released to the public, I stated in a previous blog entry, that:

The plugin used to access Internet Explorer’s rendering engine opens Netscape 8 to the same security vulnerabilities Internet Explorer has, regardless of what rendering engine is being used.

To further explain this, there is a file in the plugins folder called npTrident.dll. The name of Internet Explorer’s rendering engine is Trident. If you enter about:plugins in Netscape 8 you’ll see that the trident plugin is enabled for the MIME types text/HTML, text/plain, text/xml and application/xml. Any website that detects you are using Netscape 8, could use an <embed> to feed you an Internet Explorer exploit, even if you’re surfing in the Firefox mode.

Well apparently this vulnerability has been fixed in the final release of Netscape 8.0. (currently at 8.0.1)
For more info see http://www.stonie.co.uk/nsbvuln.html

Closing threads on secnews

There has been some recent confusion about threads in the secnews.netscape.com newsgroups being closed. I just want to make things clear for everyone.

What is this all about?
There has been too much off-topic discussion taking place on the secnews.netscape.com user support newsgroups. While camaraderie is encouraged, the utility of the user support venue is first priority. Too much off-topic discussion makes reading the group much less efficient. Those looking for technical support, may have to weed through a lot of off-topic discussion to find an answer to their problem. In some cases, an answer may not be there, because the problem may have been lost in the discussion. Those of us offering to help people with their technical problems become less efficient at solving problems, and less quick to get to the technical questions.

After being asked to stay away from off-topic discussion, most replies were in defense of such practise. Most users showed an unwillingness to adhere the request; so something more had to be done.

What is considered to be off-topic discussion?
secnews.netscape.com has newsgroups set up for user support. Each support group is dedicated to a specific product. If the discussion is not about the product the group is for, then it is off-topic.

What is the purpose of closing threads?
Closing threads is a way cutting down on off-topic discussion. This way, people will not have to compose messages with an uncertainty that the message will be deleted.

What is the criteria for a thread to be closed?
I make it a rule not to close threads in which the technical discussion is still ongoing, or the original posted problem has not been solved. Other than that, there must be an ongoing off-topic discussion. The closing of threads has absolutely nothing to do with who the original poster is, or who is engaging in the off-topic discussion. Thread closures are based on message content, not the authors.

If the above rule is exploited or abused at all, I may start partially closing threads, removing only the discussion that is off-topic.

As a general rule, if you want to discuss something that is off-topic, try to move the to an appropriate forum. Jay Garcia has set up a general discussion venue for secnews off-topic posters here.

Why are your “CLOSED THREAD” notices in reply to the original post, rather than the latest post in the thread?
I don’t want to give the latest poster the impression that the thread closure is his/her fault alone.

Why are you (Chris Ilias) the only one closing threads?
Closing threads is my responsibility alone. The rest of the Mozilla Champions have put their trust in me to choose which threads get closed, and to do the removing of messages. This is a responsibility that I asked for.

The posting guidelines say “The “Original Poster” has control of the thread”; so why is it that you can close them?
You control your threads to a certain degree. Ultimately, it is AOL’s server, and the Champions have the authority to delete posts. In the case of using AOL’s Netscape user support news server as your personal chatroom: you abuse, you lose.

Added on May 25th:

Why don’t you create a newsgroup for off-topic discussion?
We don’t have the power to create newsgroups on secnews. Even if we did, I’m not sure we would create a newsgroup for off-topic discussion (Still iffy on the issue). I mentioned the possibility of an OT newsgroup on the new Mozilla server to Gervase Markham, who replied with “OT discussion should happen somewhere where it’s on-topic. Otherwise in mozilla.general.” Yet web-based user support almost always have an OT forum. (After Dark, Lounge, General Discussion) The community is kept together, and able to discuss whatever they want. This is why Jay created a general discussion venue. I suggest you use it.

Part of why I participate on secnews, is because I’m able to talk off-topic. Either let it go, or I’m going to participate somewhere else.
This ultimatum makes me laugh. Most of the people saying it have been participating on secnews for years, yet there was never this amount of off-topic discussion, until just a couple of months ago. Why the change? Why is it, all of a sudden, so imperative? It’s not a question of ‘allow OT or disallow it’. It’s simply a case of volume. Having said that, if that amount of OT discussion is so important to you, take your OT and leave. There’s no shortage of people willing to help; and more will come due the increased efficiency.

Isn’t this censorship?
Why yes it is. Every privately owned user support venue is moderated.

Why don’t you post this URL on secnews?
To keep discussion out of the way of user support. I’ll add this URL to all of my “CLOSED THREAD” notices from now on.

Your browser is NOT outdated

Today Netscape 8 was released; so I went to Netscape.com to download it. I was automatically redirected to a detour page, with this message [click on image for the full page]:

I’m using Firefox 1.0.4. Netscape 8 is based on Firefox 1.0.3.
Folks, if you get this message, don’t believe it. It’s a lie. The only browser detection script being used is one that checks to see if you are already using Netscape 8.

As a matter of fact, if you’re using Netscape 8, your browser is outdated.

No More Address Munging

I while ago, I noticed that Google Groups‘ new Beta system does not display full email addresses. Seeing as Google is probably the most popular usenet archival engine, and thus the main source of email address harvesting for spammers, I wondered how much affect the new system had on spam.

For the past week, I have posted to usenet with a real email address. It turned out to be a total of 21 messages in both alt.* hierarchy and the netscape.* hierarchy.
I didn’t get one spam message.

It just may be time for people to stop munging their email addresses on usenet.

UPDATE: A couple of days later, I got two spam messages.

A Proper Signature

For those who didn’t know;

RFC Standard
ftp://ftp.demon.co.uk/pub/news/doc/so1036.txt

“signatures”: short closing texts, auto-matically added to the end of articles by posting agents, identifying the poster and giving his network addresses etc. If a poster or posting agent does append a signature to an article, the signature SHOULD be preceded with a delimiter line containing (only) two hyphens (ASCII 45) followed by one blank (ASCII 32).
Posting agents SHOULD limit the length of signatures, since verbose excess bordering on abuse is common if no restraint is imposed; 4 lines is a common limit..

Let’s recap:
– Your email/newsgroup signatures should be a maximum 4 lines. That’s the standard limit.
– separate your signature from the message body with two hyphens and a space (-- ). You’d be surprised what software can do if it can recognize a proper signature delimiter. 🙂

The history of Mozilla newsgroups

I have to explain this frequently; so here’s the long version.

A lot of people get confused, and sometimes mad, when they find out that all the netscape.public.mozilla.* usenet newsgroups are for development discussion, while the user support newsgroups are on a secure server, not propagated to usenet. Here’s why:

The first thing to understand is that Netscape created the Mozilla project, as a way to develop their next internet suite. When Netscape first set up their news (NNTP) server (secnews.netscape.com), Netscape had new SSL implementation in its Enterprise software with the addition of NNTP software using port 563. This is something big corporations (who were in big with Netscape) wanted badly. The Netscape news server showcased that technology. Netscape also created a subset of groups to be propagated to usenet, called “public.” (ie. netscape.public.* groups).

When the Mozilla project was created, discussion groups were needed, and for some reason, it was decided that the mozilla newsgroups would be in the .public.* hierarchy, distributed over usenet. (ie. netscape.public.mozilla.* groups) They also wanted people to be able to access the mozilla groups on the Netscape server, but for it to work properly, this requires access without an SSL connection; so an alias to the Netscape server was created (news.mozilla.org).
For clarification, secnews.netscape.com and news.mozilla.org are the same physical server. You can access the secure groups with news.mozilla.org set to an SSL connection (port 563). (The SSL certificate is for the domain secnews.netscape.com, so you’ll get a cert mismatch message; but everything will work.)

Since Mozilla was not intended for use by end-users, there was no need for user support newsgroups. The name “.mozilla.” in the newsgroup name was the indicator that the group was for development discussion. As time went by, people started using Mozilla as an end-user product, and looking for technical support. Naturally, they started posting in the developer groups.

This is when the Mozilla Organization addressed the growing problem of misplaced posts, with a bug report to reorganize the Mozilla news hierarchy. Unfortunately, administrative wheels were very slow to implement the new hierarchy. And so, as a temporary solution, user newsgroups were created on the secure server, with no propagation to usenet. They were basically placed along side the Netscape user support groups.

The current situation:
When the Mozilla Foundation was created in July of 2003, the domains had to be moved to their own servers. This includes news.mozilla.org. The problem is that they don’t have the resources to set up the server, create the new newsgroups, work out a transition plan, and maintain the server. Mozilla is currently looking for a volunteer news administrator to do that. Until that happens, all the netscape.public.mozilla.* usenet newsgroups are for development discussion, and the user support newsgroups are on a secure server, not propagated to usenet.

August 29, 2005 update:
**Giganews hosting the new Mozilla news server**

Forum Diet

You’ve seen how many forums there are for Mozilla and Netscape, right? Including developer forums, there’s no way a normal human being can keep up, let alone participate. And so, I’m going on a forum diet.

Most notably, I’m no longer participating in netscape.mozilla.user.win32.
I don’t have the time to participate in netscape.public.general, or alt.netscape. I did some support in the UFAQ forums, but not anymore.

I started doing Netscape support in alt.netscape, so I’m still hesitant about leaving that one.

In which newsgroups am I still giving tech support?
netscape.mozilla.firefox
netscape.mozilla.thunderbird
netscape.mozilla.user.general
netscape.netscape7.windows

The only web-based forums I’m going to do support in (on occasion) is Mozillazine’s Thunderbird and Seamonkey support forums.