Forgot your password?

typodupeerror

Comment: Re:Geocities as a blogging site? (Score 1) 160

by hobarrera (#43807747) Attached to: Yahoo Pinkie-Swears It Won't Ruin Tumblr

I trust yahoo. They let sevices stagnate and leave them without change for years.
Google changes the UI to most of it's stuff almost yearly with almost no new funcionality, and keeps shutting down services.

I'd rather have a 5 years old GUI, and have my service shut down. (ie: reader, caldav, soon: xmpp).

Comment: The reason I don't use Yahoo's services... (Score 1) 160

by hobarrera (#43801293) Attached to: Yahoo Pinkie-Swears It Won't Ruin Tumblr

The reason I don't use Yahoo's services is simply that it's impossible to remember your username.
Yahoo forces you to register an email if you want a yahoo account. There's two problems with that:

1. It's impossible for create a rememberable username. You need to append three digits to any username to create one that isn't taken and...
2. I don't even want an @yahoo.com email. I already have email, thanks. Just let me use my existing one as a username.

Comment: Old news? (Score 1) 410

by hobarrera (#43777979) Attached to: Google Drops XMPP Support

This is old news. This was one of the first comments on the "Google releases Hangouts" a few days ago.
I've lost contact with about 40% of my contacts so far. Of those whom I can still talk to, about 20% use google with an xmpp client, and the other 40% are not google users (they use some other XMPP server).

Comment: Re:Even more vendor lockin (Score 1) 115

by hobarrera (#43766703) Attached to: Google I/O 2013 Underway: Watch For Updates

That would not be a new standard. That would merely be a new protocol, which they publicly documented. There's a big difference.
Documenting it isn't enough either. Do all those other xmpp users out there need to migrate their servers and clients too? Just because google wanted to use a new protocol? I don't think so.

No, actually, there isn't a difference. You can pretend that somehow the IETF magically turns RFCs into "standards", but a standard is merely something publicly defined that people can follow.

It's not a standard because the IETF published it. It's a standard because there are dozens of client and server implementations, and thousands of running servers out there. If google opens up their spec, it'll still be just one server. And there'd be no point to a second server out there, because they don't federate.

If it's so outdated, why do facebook, wlm and whatsapp use it internally? Granted, they don't federate, but they still use the protocol.

WLM uses MSNP2, not XMPP.

None of those do video chat, either. And just because they use it doesn't mean it's a good decision or not outdated. XMPP is not mobile-friendly

WLM supports XMPP for some time now, though with a custom auth mechanism. Do you googleing before arguing.
As for non mobile-friendly: {{citation needed}}. Also, whatsapp uses XMPP, and their service is the most popular on mobile platforms.

Ask not what's inside your head, but what your head's inside of. -- J.J. Gibson

Working...