If this rumor is true, and I run my own Jabber server, can my users connect through my server into Google's users?
That's a good question. At this moment, talk.google.com doesn't seem to be listening on port tcp/5269 (which is the standard Jabber/XMPP port for server to server communication), and c2s seems to require some special type of SASL authentification (maybe to discourage users to try connecting with a non-google Jabber client when the service starts). Of course, maybe they will enable s2s (and thus syndication with the rest of the Jabber network) when they officially roll out the service.
Speculations, speculations... Let's just wait till tomorrow and see, shall we?
Update: There is now a petition to keep Beastie, however FreeBSD's own Robert Watson emailed us to inform us that they are "seeking a new logo, but not a new mascot", so that petition is really reduntant.
Update 2: Rob Watson writes:
- The announcement text was an early draft, and the contest hasn't been announced yet.
- One of the immediate pieces of feedback we got was that we need to make it more clear: this is not about replacing the beastie!
- We're looking to create a new logo that can be used with the Beastie, or by itself. One of the specific concerns we have is that the daemon renders poorly in print using one-color, two-color, etc, and we need a vector logo, not just a mascot. Another was finding a logo that could be conveniently and easily printed by vendors on packaging for products that support FreeBSD. Not all vendors are willing to stick a Daemon on their packaging!
- We anticipate releasing the real announcement in the near future, at the logo-contest.freebsd.org URL. When it's ready, we'll send out e-mail to freebsd-announce, and we'll drop you a direct e-mail.
- Once again we've been reminded of an important lesson: don't put something on the web site if it's not ready to be seen. After at least three premature postings of FreeBSD releases on slashdot due to files starting to appear on the FTP mirrors even though the announcement hadn't been sent, you'd think we'd have learned.
There are no "official" Jabber libraries, or an official API, in the same way that there are no official e-mail, HTTP or IRC libs. A proposed standard is used as a guideline for programmers, and allows many independent implementations.
Also, note that XMPP is a protocol that powers the Jabber IM system, but XMPP can be used for other things beside instant messaging. So, the bottom line is, when you work on a Jabber you're working with the XMPP protocol.
If it doesn't do so out of the box, then that's not relevent. The vast majority of people are not capable of, or interested in, XUL configuration.
I don't understand what you mean. When you install Mozilla 1.0 out of the box, the Classic theme is the default, and it DOES feel like a native win32 app (colors, fonts, widgets, drag'n'drop).
What about Unicode support? GNOME 2, based on the new GTK+ will supposedly support Unicode all over the place. Is this true with KDE 3/Qt 3 also?
I recently tried Windows XP, and it offers great support for Unicode. It is time to get the UNIX desktop moving in that way. I know it's not much of an issue for the English speaking world, but it is a very important thing for most of the non-English users.
ICMP is used for passing control and error messages (thus the name -- Internet Control Message Protocol) between hosts(ie. an error message if a datagram couldn't reach it's destination, or it could be used by a gateway to tell the host that there is a shorter route it can send packets by). the messages are used internaly by the IP protocol, so they're not so apparent to the user.
the best reading is probably the RFC792... here:
http://www.cis.ohio-state.edu/htbin/rfc/rfc792.htm l
Slashdot Mirror
Since V4.23 (released on the 29th of July) 7-Zip supports drag'n'drop.
If this rumor is true, and I run my own Jabber server, can my users connect through my server into Google's users?
That's a good question. At this moment, talk.google.com doesn't seem to be listening on port tcp/5269 (which is the standard Jabber/XMPP port for server to server communication), and c2s seems to require some special type of SASL authentification (maybe to discourage users to try connecting with a non-google Jabber client when the service starts). Of course, maybe they will enable s2s (and thus syndication with the rest of the Jabber network) when they officially roll out the service.
Speculations, speculations... Let's just wait till tomorrow and see, shall we?
Mod parent up.
From OSNews.com:
Update: There is now a petition to keep Beastie, however FreeBSD's own Robert Watson emailed us to inform us that they are "seeking a new logo, but not a new mascot", so that petition is really reduntant.
Update 2: Rob Watson writes:
- The announcement text was an early draft, and the contest hasn't been announced yet.
- One of the immediate pieces of feedback we got was that we need to make it more clear: this is not about replacing the beastie!
- We're looking to create a new logo that can be used with the Beastie, or by itself. One of the specific concerns we have is that the daemon renders poorly in print using one-color, two-color, etc, and we need a vector logo, not just a mascot. Another was finding a logo that could be conveniently and easily printed by vendors on packaging for products that support FreeBSD. Not all vendors are willing to stick a Daemon on their packaging!
- We anticipate releasing the real announcement in the near future, at the logo-contest.freebsd.org URL. When it's ready, we'll send out e-mail to freebsd-announce, and we'll drop you a direct e-mail.
- Once again we've been reminded of an important lesson: don't put something on the web site if it's not ready to be seen. After at least three premature postings of FreeBSD releases on slashdot due to files starting to appear on the FTP mirrors even though the announcement hadn't been sent, you'd think we'd have learned.
Robert N M Watson
There are no "official" Jabber libraries, or an official API, in the same way that there are no official e-mail, HTTP or IRC libs. A proposed standard is used as a guideline for programmers, and allows many independent implementations.
Also, note that XMPP is a protocol that powers the Jabber IM system, but XMPP can be used for other things beside instant messaging. So, the bottom line is, when you work on a Jabber you're working with the XMPP protocol.
(to "chunder" is to vomit) "Living in the land Down Under
Where beer does flow and men chunder"
If it doesn't do so out of the box, then that's not relevent. The vast majority of people are not capable of, or interested in, XUL configuration.
I don't understand what you mean. When you install Mozilla 1.0 out of the box, the Classic theme is the default, and it DOES feel like a native win32 app (colors, fonts, widgets, drag'n'drop).
What about Unicode support? GNOME 2, based on the new GTK+ will supposedly support Unicode all over the place. Is this true with KDE 3/Qt 3 also?
I recently tried Windows XP, and it offers great support for Unicode. It is time to get the UNIX desktop moving in that way. I know it's not much of an issue for the English speaking world, but it is a very important thing for most of the non-English users.
ICMP is used for passing control and error messages (thus the name -- Internet Control Message Protocol) between hosts(ie. an error message if a datagram couldn't reach it's destination, or it could be used by a gateway to tell the host that there is a shorter route it can send packets by). the messages are used internaly by the IP protocol, so they're not so apparent to the user.
m l
the best reading is probably the RFC792... here:
http://www.cis.ohio-state.edu/htbin/rfc/rfc792.ht
You're right... Actually, I think there are 23 *pairs*, and each of them consists of two identical chromosomes.