Ah, but Google tells that they actually are registered:
page, Google Cache (because it didn't want to load for me for some reason) - that was the first result too.
I would recommend against spamming those addresses, or even calling that phone number - we don't want to hurt innocent unrelated people. The e-mail address may even be some contact from some under company, since it's at a different domain and all.
Information on ejobz.net, Inc. would be interesting though.
Considering that this particular contest is something that Google would likely want to discourage, since search engine spamming would hurt their credibility (by returning less relevant results)...
I wonder if Google would special case this search (manual intervention, as I believe has been done before) to have the top search point to their own page or something...
Ummm... I'm pretty sure it depended on the CRT used - plug into a green monitor, you get green text. Plug into a colour monitor (*), you get actual white text.
(*) Some old colour monitors had cables / sockets that would let you plug into monochrome video cards - I had one of those.
I believe the stats come from tinderbox (automated builds), which are now also being used to build nightlies. As the nightlies are not debug builds (it would be a pain to download, for one thing), my guess is that those stats are for non-debug builds.
Phoenix, (now Firefox) never really was independent. It was mostly a rewrite of the user interface; you still get Firefox by downloading the Mozilla sources (trunk) and setting a build flag. As such, there really is nothing to remerge - they share the rendering engine, network stuff, etc. Pretty much anything none-UI.
The Firefox project pretty much forks on releases (kinda like how the main Mozilla project forks on suite releases) and merges back into the trunk. Appearently Firefox 0.9 / 1.0 will be based off the Mozilla 1.7 branch and merge after 1.0 though.
(Well, okay, so they've been working on profile migration, and I don't think that's being used by the suite yet... But that part is also pretty buggy right now.)
Appearently bits like the MIME handling was copied from the old codebase.
Or at least that's what somebody said in the MHT (RFC 2557) saving bug; I'm not linking hopefully to avoid/.'ing bugzilla via people with referrer blocking. See comment 82 of that bug.
UAs send things like browser and O/S because it can be used for good: if the server sees that you're, say, minimo running on Zarus (PDA), it could potentially send you a stripped-down version of the page with minimal non-content fluff. Or at least redirect you to one such page.
Unforunately, it's the bad browser sniffing that turns up the most - making hacks such as IE proclaiming itself as Mozilla/4.0 (Compatible) necessary.
You actually need to manually drag the link to the tab bar, instead of just opening the link in a tab.
I think what's happending is that, by using the drag, you confuse the browser enough that it can't tell where the link was (because allt he receiving end sees is the URL).
I'm pretty sure it doesn't go back to the NCSA codebase, considering that I remember seeing a Netscape history page explaining that this came from "Mosaic" + "Godzilla", something about crushing Mosaic...
(Take this with a grain of salt, since I can't be bothered to find the source right now)
Slashdot Mirror
Ah, but Google tells that they actually are registered:
page, Google Cache (because it didn't want to load for me for some reason) - that was the first result too.
I would recommend against spamming those addresses, or even calling that phone number - we don't want to hurt innocent unrelated people. The e-mail address may even be some contact from some under company, since it's at a different domain and all.
Information on ejobz.net, Inc. would be interesting though.
Considering that this particular contest is something that Google would likely want to discourage, since search engine spamming would hurt their credibility (by returning less relevant results)...
I wonder if Google would special case this search (manual intervention, as I believe has been done before) to have the top search point to their own page or something...
The whole thing also needs Win 2k+. So you'd need that anyway - you're still saving money on getting the compiler (I'm assuming the IDE isn't free)
.NET SDK download, as mentioned before.
P.S.
I'm fairly sure it also uses VBScript. At least it does in the containing frame.
I doubt anybody other than MS would support that anytime soon...
Ummm...
I'm pretty sure it depended on the CRT used - plug into a green monitor, you get green text. Plug into a colour monitor (*), you get actual white text.
(*) Some old colour monitors had cables / sockets that would let you plug into monochrome video cards - I had one of those.
Sun, on Win32 at least.
It would complain, for some reason. Oh, and it would also crash if your UA was too long... 20-something characters IIRC.
I believe the stats come from tinderbox (automated builds), which are now also being used to build nightlies. As the nightlies are not debug builds (it would be a pain to download, for one thing), my guess is that those stats are for non-debug builds.
Phoenix, (now Firefox) never really was independent. It was mostly a rewrite of the user interface; you still get Firefox by downloading the Mozilla sources (trunk) and setting a build flag. As such, there really is nothing to remerge - they share the rendering engine, network stuff, etc. Pretty much anything none-UI.
The Firefox project pretty much forks on releases (kinda like how the main Mozilla project forks on suite releases) and merges back into the trunk. Appearently Firefox 0.9 / 1.0 will be based off the Mozilla 1.7 branch and merge after 1.0 though.
(Well, okay, so they've been working on profile migration, and I don't think that's being used by the suite yet... But that part is also pretty buggy right now.)
I believe it's something about how big corporations (as in, the people actually paying for things) prefer the suite.
I'm not sure how accurate that is though - this is just stuff picked up on the MozillaZine forums and other user-submitted comments.
Hmm, can you provide more information on the crash using phpBB? O/S. version, etc.?
(I find the bug interesting, because MozillaZine - pretty much the semi-official forums for Mozilla - runs phpBB.)
Appearently bits like the MIME handling was copied from the old codebase.
/.'ing bugzilla via people with referrer blocking. See comment 82 of that bug.
Or at least that's what somebody said in the MHT (RFC 2557) saving bug; I'm not linking hopefully to avoid
UAs send things like browser and O/S because it can be used for good: if the server sees that you're, say, minimo running on Zarus (PDA), it could potentially send you a stripped-down version of the page with minimal non-content fluff. Or at least redirect you to one such page.
Unforunately, it's the bad browser sniffing that turns up the most - making hacks such as IE proclaiming itself as Mozilla/4.0 (Compatible) necessary.
You actually need to manually drag the link to the tab bar, instead of just opening the link in a tab.
I think what's happending is that, by using the drag, you confuse the browser enough that it can't tell where the link was (because allt he receiving end sees is the URL).
I'm pretty sure it doesn't go back to the NCSA codebase, considering that I remember seeing a Netscape history page explaining that this came from "Mosaic" + "Godzilla", something about crushing Mosaic...
(Take this with a grain of salt, since I can't be bothered to find the source right now)
What scares me is that the article states the bug "...goes back to release 20 (from 1997)." They didn't think they'd be around in 7 years?
This is scary.