OpenIM? I was thinking of OpenFire. Jabberd2 may be a mess, but I think it still counts as major. And it is a separate C++ codebase for Jabber that could be fixed up if anyone need to/wanted to.
I read the thread at several different times and I guess I missed your comment, because I didn't see it until my last pass over the thread. Sorry about that.
>Why on earth do projects like Epiphany even exist, because they want a browser that had better gnome integration, and was lighter weight because it used GTK, and not XUL.
Anyway, just hold your horses, Epiphany will be webkit based soon enough. And there has been a fair amount of unforking between khtml and webkit.
Re:When in doubt, fork off.
on
Cisco To Buy Jabber
·
· Score: 3, Informative
How does stuff like this get post and modded insightful, when there are already numerous post stating that:
1. the protocol is open 2. OSS licenses can't be retroactively revoked 3. The Jabber Inc product, Jabber XCP, is not and never has been Open Source. 4. There are 3 or 4 major OSS xmpp servers already, and several smaller ones (and none of these have been bought).
Well, Jabber Inc owns Jabber XCP, which is closed already.
Jabberd 1.4 and Jabberd2 are not owned, controlled or even affiliated with Jabber Inc. Openfire and ejabberd are likewise not connected to Jabber Inc. Furthermore, all are FOSS and the license cannot be revoked.
As for XMPP itself, it is managed by the independent, non-profit XMPP Standards Foundation, and the core of XMPP also exists as several Standards Track IETF RFCs.
>Mozilla is quite understandably protective of its Firefox trademark,
I think you mean "insanely overprotective of it's Firefox trademark". Mozilla has restrictions that no other FOSS project I know of has, all to "defend their trademark". But Linux, Apache, Gnome and KDE, to name a few, are all trademarked and they don't have those restrictions. Combine that with pointless EULAs, and non-free artwork, and you have a project that doesn't measure up as FOSS.
SeaMonkey 1.x is less than 90% the same code as FF. A lot of extensions work, but there are plenty that don't.
SeaMonkey 2.0 will share much more code with FF and will have "the "bad site" warnings, plugin auto-upgrade checks, the little warning bar that drops down from the top to tell you things" and it will have more extension compatibility and probably the awesomebar as well.
Slashdot Mirror
>A 128bit addresses space really is enough for anyone. No, really.
Until we setup an intergalactic, multiuniversal network.
>1.
true
>4.
OpenIM? I was thinking of OpenFire. Jabberd2 may be a mess, but I think it still counts as major. And it is a separate C++ codebase for Jabber that could be fixed up if anyone need to/wanted to.
anyway there is a complete list here:
http://en.wikipedia.org/wiki/List_of_XMPP_server_software
There are more than I thought.
I read the thread at several different times and I guess I missed your comment, because I didn't see it until my last pass over the thread. Sorry about that.
>Why on earth do projects like Epiphany even exist,
because they want a browser that had better gnome integration, and was lighter weight because it used GTK, and not XUL.
Anyway, just hold your horses, Epiphany will be webkit based soon enough. And there has been a fair amount of unforking between khtml and webkit.
How does stuff like this get post and modded insightful, when there are already numerous post stating that:
1. the protocol is open
2. OSS licenses can't be retroactively revoked
3. The Jabber Inc product, Jabber XCP, is not and never has been Open Source.
4. There are 3 or 4 major OSS xmpp servers already, and several smaller ones (and none of these have been bought).
>unless they intend to end the open source licensing.
Jabber XCP is not OSS
Well, Jabber Inc owns Jabber XCP, which is closed already.
Jabberd 1.4 and Jabberd2 are not owned, controlled or even affiliated with Jabber Inc. Openfire and ejabberd are likewise not connected to Jabber Inc. Furthermore, all are FOSS and the license cannot be revoked.
As for XMPP itself, it is managed by the independent, non-profit XMPP Standards Foundation, and the core of XMPP also exists as several Standards Track IETF RFCs.
Didn't someone already come up with carbon nanotube solar cells, and a tower design? It seem like I read this stuff in Science News or someplace.
>We have seen allot of theoretical technical innovation in solar and battery technology in the past 10 years with little new technology in production.
There is plenty of new solar technology in production. It is just a little harder to see than 40 foot windmill blades.
MySQL, Xen and Zope are trademarked, but their policies haven't caused problems in Debian or other distros.
Vote cast!
>What bothers me more is that the logo is an empty globe instead of the better looking one with the fox.
The name Minefield and the different logo is to indicate that it is not an official release.
>Mozilla is quite understandably protective of its Firefox trademark,
I think you mean "insanely overprotective of it's Firefox trademark". Mozilla has restrictions that no other FOSS project I know of has, all to "defend their trademark". But Linux, Apache, Gnome and KDE, to name a few, are all trademarked and they don't have those restrictions. Combine that with pointless EULAs, and non-free artwork, and you have a project that doesn't measure up as FOSS.
>That's a mistake so fundamental that the protocol should be thrown out.
One old implementation is doing the wrong the thing, so the whole protocol should be thrown out? That's ridiculous.
Nothing is stopping you from using any open client with gtalk.
well, 8.5 came out back in Q3 2005, so it has been about 3 years.
they dropped ads in 8.5, current version is 9.5
If that's the British DHS, the American counterpart is Home Depot, and it should be obvious why they'd want to spy on people.
So they can tell if you have been going to Lowe's?
XMPP
I am glad someone pointed this out.
What does Java have to do with this story?
Like stupid simple multimedia.
like SVG, <canvas> <audio> and <video>
JS drives most of GUI interaction in FF. The bulk of the C++ is down in gecko, for rendering speed.
SeaMonkey 1.x is less than 90% the same code as FF. A lot of extensions work, but there are plenty that don't.
SeaMonkey 2.0 will share much more code with FF and will have "the "bad site" warnings, plugin auto-upgrade checks, the little warning bar that drops down from the top to tell you things" and it will have more extension compatibility and probably the awesomebar as well.
You don't make backups?