Tags or Labels? Which one do you prefer?

I read a this post on Niall Kennedy’s blog about the new features in the Google Toolbar which includes the ability to store and tag label bookmarks that can also later be retrieved when logging into a different machine.

While the concept is nice (and is similar in a number of ways to the del.icio.us extension for FireFox the thing that caught my eye was the fact that Google decided to call the tags labels.

While they (Google) are very consistent with the naming issue (you also have labels in Gmail) why is the term “labels” was chosen over “tags”?
Do they think that the term “labels” is easier to understand and explain to the common John Dow instead of “tags”?
Did they do it just to set themselves apart from the whole “tagging” frenzy going on, or did they simply chose this term before the “tags” term went very public?

Anyhow, I personally prefer “tags” over “labels”. When I say “labels” I always have a connotation of sticky notes on boxes.

Which one do you prefer, Tags or Labels?


I know it has been a little quite around here and on my other blog.
I may have hinted a bit in the past that I’m involved in this new and cool project but if I didn’t, I’ll say it out loud, I AM INVOVLED IN A COOL PROJECT :-)

That’s the main reason for the quiteness.

This project is called Yedda and you are more then welcome to visit the site and the Yedda Blog to get more information.
It’s soon about to roll out into beta so be sure to apply for it.

Connect Google Talk with MSN, Yahoo and AIM

Just saw this on Digg and since I’m already on a Jabber frenzy due to my previous posts, I thought I should share.

Looks quite cool, though I haven’t tried it yet.

I’m using GAIM so I got everything all up in one client. I’m just waiting to get a build of GAIM that works with libjingle so I would be able to chat with my friends using Google Talk’s voice features.

If I only had a bit more free time to actually code on GAIM that would be even better… oh well… back to the salt mines.

Technorati : , , , , , , ,
Del.icio.us : , , , , , , ,
Ice Rocket : , , , , , , ,

Gmail dot Scandal

I’m sure you’ll all have heard about the Gmail dot scandal and that it WAS confirmed by Google.

I’m not a heavy Gmail user but I do have an Email box there (like everyone else) but it DOES pisses me off, specifically since my Email HAS a dot in it.

This can also explain why I got an Email a while back from someone that claimed to be my wife (although she was referring to another Eran Sandler ;-) ).

If this was complained that long how come it wasn’t fixed? It’s outrageous that someone else, in certain cases, will be getting my private Emails. I feel so violated.

I just hope they’ll get their act together and fix this before all hell will break loose. They have enough privacy issues/concerns right now to deal with and I’m sure the folks at Google are not in the mood for another one.

Company-Wide Instant Messaging with Jabberd

Continuing my current fixation about Jabber and Jabber related stuff (it all started with this post about how Google is openning up Google Talk to talk with other Jabber based servers), there is a good article up on O’Relly’s OnLamp.com about the pros and cons of a Company-Wide Instant Messaging solutions as well as how to setup Jabberd 2.x to do just that.

It’s really worth the read for people that are trying to figure out how to utilize an IM solution in their company while still retaining a high degree of security.

Go. Read. Implement.

Jabber Servers Supporting the DialBack Protocol

I promised in the previous post about Google Talk’s support for federation to check what open source Jabber servers supports the DialBack protocol described in RFC 3920 used by Google Talk server to talk to other Jabber server.

Well… it seems that the dialback protocol is supported by all server listed here and a bunch of other non open source servers not listed there.

This is a good thing, but it seems the dialback protocol is not encrypted like the other TLS and SASL server-to-server protocols. On the other hand all other IMs today are not encrypted by default so privacy issues regarding this are legitimate as to the rest of the IMs available.

The main advnatage of the Jabber Protocol (besides it being an open source specification and a standard) is that it is federated like the Email system is, meaning, if I send an Email to another friend who is on the same server, that Email will never leave the server.
If I send an Email to a friend in a different server (domain) that Email can go through 1 or more other servers until it reaches its destination.

This is a great oppertunity for business who are afraid of putting instant messaging software inside the organization due to security issues since all internal IMs will be kept internal and will not travel outside the network of the company/office/department/group. Only when IMs will go to a user on a different network they will be sent to a differnet server.

In addition to that, and as I talked a bit in an earlier post, Jabber has support in the protocol for cross-protocol communications, which means that upon installing a bridge to a different IM system (MSN, Yahoo, AOL, ICQ) you can use your internal Jabber client, see other IM users from your corporate as and users from other Jabber servers as well as users from other networks such as MSN, Yahoo, AOL and ICQ.

Now all we have left to do is promote the proposed standards for Jingle (JEP-0166) and Jingle-Audio (JEP-0167) (and perhaps the open source libjingle library) so we will finally bridge all the gaps between the various IM systems we have today.

Someone heard my call – Google Talk support federation

A while back I posted a request/hope that Google Talk will open up to AOL using one of the Jabber bridges.

I also secretly hoped (meaning, I forgot to blog about it) that since Google Talk uses Jabber, they will open up its federation abilities and enable everying Google Talk user to communicate with any other Jabber user (providing that that user supports the necessary XMPP spec that Google Talk uses, which I still don’t know if it is one of the common ones, but I’ll check that up).

Well… Yesterday one of the Google Talk team members announced it on the Google Talk blog and it was also announced in the official Google blog.

Way to go Google!

Now almost everyone with a Jabber account will be able to talk to any other Google Talk user.

Check back here for a summary of all Jabber server that supports the dialback protocol (RFC 3920) so you’ll know which Jabber server will be able to talk to Google Talk.