So, I can only assume you don't use IM (Google Chat, AIM, Facebook chat, or IRC) or SMS, nor do you make use of, say, an ISP or telephony company, right?

I really don't understand what you mean. Of the communication methods you list I use XMPP (Google chat), IRC, SMS, telephone. I also have a website, email address and a contract with an ISP.

None of the above tie me to a single operator. If I lose trust in any of network operators or software providers involved, I can change to another one without significant service disruption -- or my contacts noticing it.

Could you clarify the question?

I assume you are referring to the Google VOIP service that is currently available to ~4.5% of the world population?

Enforcing any kind of sane network security policy with skype is impossible.

Verifying Skype message security is very difficult: we just have to take their word for it.

Skype head of security said "I will not say if we are listening in or not" when asked about eavesdropping. Apparently they have the means anyway.

Oh, and the most important thing: why the fuck would anyone want to give control of a communication network to a single company when it's not physically required? That makes no sense.

"We're closing down the service" was the main message. It's awesome if you and others familiar with GOG knew the whole deal, but the intention was clearly to deceive the media and the public. Take a look at the last /. discussion: a lot of people fell for it.

It's not like this is a big deal but it was clearly dishonest.

I can't think of a single person whom I would want up to the minute updates on.

If this is what all your friends are doing, may I suggest the problem is with them, not the medium?

How about you start licensing it with non nazi-like licences. ... But then, I suppose some people LIKE nazi-like licences.

Software license can often be negotiated: Authors may be willing to relicense (or add another one), if given a well presented and compelling argument for the change. This has happened before -- picking the right license can be difficult and it's possible the original authors did not think of all scenarios.

Speaking of "a well presented and compelling argument": you, sir, did not make one.

Maybe it tells you nothing useful, but to a bug reporter the bug is TREMENDOUSLY IMPORTANT and they very much hope that you FIND IT USEFUL.

Easy cowboy, no need to shout. I only explained why the number is not a useful statistic for evaluating the quality of development. Your experiences, as interesting and useful for improving the Mozilla development process as they may be, are not relevant to that argument.

Please realize that my argument had _nothing_ to do with the source license or development model, just the difficulty of evaluating software QA process efficiency. Bugs get lost, forgotten and buried in proprietary development and open source, working with any massive bug database will teach you this. Saying "453 BUGS!!!" does not tell us whether Mozilla is doing well or not.

It's not about the Google apps: every OS manufacturer has closed apps. The major point here is being part of the Android ecosystem: most importantly the application market. According to Skyhook, Motorola would have been banned from the marketplace if they had used Skyhook (because Android certification is a requirement and Google won't certify skyhook-enabled devices).

There may be good reasons for this: as I mentioned elsewhere, maybe Skyhook couldn't implement the location API well enough. We can't tell at this point.

No android certification, no Android app Market. That is way more important than the Google name.

You know what they about statistics... just showing a number like that isn't the whole truth. Omitting context here is not lying but it is dishonest.

As an example, you could have mentioned that your list includes bugs from _all_ products in the Mozilla bugzilla, things like Venkmann, a js debugger that hasn't existed for five years or so. You could also have mentioned that 453, while an impressive number of forgotten bugs is actually 0.075% of all reported bugs. Or you could have noted that the vast majority or those bugs only have 0-5 votes which in b.m.o means a very obscure bug, and that most of the remaining bugs don't really belong in Critical...

I'm not claiming that the those bugs don't include real, important bugs, I'm saying your figure alone tells us _nothing_ useful. B.m.o is a massive and ancient issue tracker, things do get lost in there, but that doesn't prove that the process is totally broken. If you can't understand this, then you haven't worked with massive issue trackers. In the corporate world this problem is often "solved" by a QA cleanup: sweep under the rug any issues that are too obscure and where no progress is being made. That looks a lot better in the reports but doesn't really help the users.

Look, it's not about "actively stopping the use of Skyhook", no-one is claiming that! What end users can do is just not relevant. This is all about OEMs and what they are allowed to do: Skyhook is saying that Google now prevents OEMs from using a service that competes with Google if they want to be part of the ecosystem.

Google Maps has no technical reason to require exactly the Google location implementation, anything that provides the same API should do. But even if you were right, Google isn't just demanding their location services for Maps to work: According to Skyhook OEMs that do not use Google location services cannot be Android compatible, meaning no Android market, no gmail or anything in the ecosystem for them.

I have no idea if Skyhook is telling the truth -- they could be omitting details like not being able to implement a good replacement for the Google location component. But if they are mostly correct, I think this is a big deal -- it shows that openness only goes so far if you are an OEM... when you start competing with Google, you may get kicked out. This isn't inherently bad, but good to know.

All actual data like messages is (supposed to be) encrypted. So the rogue seed can see your network or parts of it but should not get anything else.

My understanding is from a quick glance, it would be awesome if the developers would document things a bit more and lay out the design and roadmaps properly.

sure, it goes against the idea that android is supposedly completely free/open, but google has a right to protect their platform, and the experience on that platform

This, I believe, is the only problem here -- Apple does everything exactly like Google with the exception that they don't claim to be "open". Likewise Intel doesn't say Centrino is about choice in anyway. Google does, according to Daring Fireball Vic Gundotra says "If you believe in openness, if you believe in choice, if you believe in innovation from everyone, then welcome to Android". Now maybe he meant Android the base operating system, but I would have thought he meant the Android ecosystem -- OS, software, services, market...

I think what you said is 100% true: Google has every right to stop you from using the Android name if you do anything Google doesn't like. But the fact remains, calling that an open system is dishonest.

In this particular case I can't accept that they are just protecting the integrity of the platform: do you think Google would have done this if location wasn't a Google service? Would Google really have forced every manufacturer to use e.g. Skyhook if they thought Skyhook was really good?

Read the summary at least :)

OEMs are not allowed to ship other location products, or they lose their access to Google services, the market, etc. So the operating system itself is really open, but the ecosystem around it is "open as long as you do what we tell you to do".

You physically cannot make that impossible. You could encrypt messages and things like that but your service provider must know quite a few things, like your friends service IDs. Putting a lot of effort in this is a fools errand: you need to trust you service provider to a large extent (not just in social networking, but in any networking).

Also, many people are fine giving their personal info in exchange for better service. Why should that be impossible -- as long as there are other options for the privacy conscious? The important point is that users must be able to move from one provider to another.