Flux RSS

Sunday, July 3 2011

Google Plus is the new Wave

Okay, okay, the pun is bad. But still. If you managed to enter Google Plus, and was a user of Google Wave before, the similarities are insanely obvious. And I'm pretty sure I understand better now what happened to Google Wave.

In one of my previous entries, I ranted about how Google let Wave died. But I was wrong. They didn't let it die, they had an internal struggle within Google about where to go and what to do.

I'm pretty sure that was happened is the following: Google Wave was seen by some as the "new e-mail" standard, and they were trying to establish protocols and make it as open as possible so to let others to integrate with them, just as I described before, but others were seeing Google Wave as a good candidate for Google's social platform, given how they went to integrate a lot of social widgets into it, and how they tried to let it as closed-source as possible. And, yes, gmail being the second major Google product, why would they want to kill it ? But Orkut being a failure, they needed something to compete with Facebook.

So of course, these two conflicting ideas weren't possible. Which is why they "let Google Wave go", into the open, as an Apache project, so it may very well become the next e-mail platform. But internally, people continued working from the original Google Wave design, and pushed the social aspect even further. That project eventually became Google Plus. There's really no doubt about it: that is the vision some of the Googlers had when they saw Google Wave as a social network, and not as a communication platform. And quite frankly, it's great. I'm now grateful that they turned away from Google Wave, letting it grow outside of Google, and that they created Google Plus instead. This is a major, awesome upgrade from the Facebook+Twitter experience. It feels good and the sensation of control over your data is fantastic.

Good job Google, and good luck.

Thursday, March 3 2011

Why "open source" is good

Not so long ago, I made a post explaining Why open source is bad. I'll try to redeem a bit myself and try to explain why there are some very good aspects of it, and why closed source is sometime excessively bad. As I mentioned in my previous post, I don't think open source should be used as a selling point in the "it's open source so it has to be good" way. Instead, it should be used as a selling point in the "we're transparent" way.

Continue reading...

Friday, February 18 2011

IPv4 is dead, all hail IPv6

A few years ago, I remember posting very angry comments about Rani Assaf's "IPv6 is just a gadget" post. Not so long after, his company introduced IPv6 natively for their customers. A few days ago, the last /8 IPv4 blocs got allocated, marking the end of the IPv4 allocation. I guess it wasn't that much a gadget, huh ? Even though the IPv4 sub-allocation is pretty poor (only roughly 14% of the addressable space is actually in use, if I'm not mistaken), the increasing complexity of the addressing space really makes life difficult.

Without even talking about the fact that IPv4 has a lot of flaws that IPv6 natively corrects. I've heard various comments claiming that this isn't so bad, that solutions exist to still use IPv4 nontheless, etc. But I'm happy to see that things are still moving towards IPv6 in general, as even the Obama administration is in favor of IPv6.

Anyway, don't worry. This blog will continue to run even if you don't have IPv4 connectivity anymore: ipv6 ready

Yay!

Monday, January 17 2011

Why "open source" is bad

This one came a long way. I'm an active open source supporter, and I probably intend to stay that way for quite a while, but I finally came to realize that open source is sometime a very bad thing. But let me explain before you start throwing tomatoes at me.

Continue reading...

Tuesday, January 4 2011

How to fail encryption, part 2

One of the very first post I've made was talking about encryption, and how to fail it. Okay, that was a very easy encryption, but the base principles remain the same: don't be stupid, aka, know what you're doing. Well, I'm joining the bandwagon here, but it seems Sony's programmers didn't really try to understand their crypto handbook, and implemented it without really knowing what they were doing. As a result, all of the private keys for the PSP and the PS3 (including the one hardcoded in the CPU die) are leaking with simply two signatures made with them.

Good job, really.

Source: fail0verflow

- page 3 of 7 -