I suspect unlimited will function like a current libraries, much like Netflix is an alternative to blockbuster not the theatre or purchases. Similarly Unlimited probably won't have the latest and greatest, rather slightly older books and series before a new one is released. (Series often sell for $1.99 or even free to promote the newer books)

From some of the stories we've had in Canada, its probably less tech companies and more banks etc. replacing their IT groups with a third-party contractor that only hires imported workers.

Sorry but your reasoning is bullshit. Before the internet people blamed cable tv, before cable it was music or tv or radio, the reality is that you're choosing not to read.

I'd say there is logic in not bothering to make the change, it takes effort and brings no value. My experience has been that gendered pronouns are often used in documentation, though usually they use a mix of the two genders.

That said there isn't logic in attempting to revert the commit when another committer merged it (unless the rule was that documentation would use a gendered pronoun). Though I also don't think the tone and content of Joyents post is appropriate either.

I question whether the author has any right to release it at all. Sounds like it was done as a work for hire thus she doesn't doesn't own the copyright.

I believe the point is that the drop down menu includes all the search providers. Personally I would like this, seems like I always have Wikipedia selected when I want Google and Google selected when I want Wikipedia.

This doesn't work. The issue isn't a node connecting to the network and having access to all data, the issue is that any user's home node explicitly has access to anything the user has been granted permission to.

I fail to see how that matters. The user you're sharing with is authenticating with their home server, thus their home server can readily impersonate them.

So unfortunately this means there really aren't any open source alternatives.

Unfortunately the distributed model has fundamental privacy problems. One needs complete trust in all server nodes as they can do nearly anything with a user's data after they have access. e.g. a user can revoke permission but that doesn't prevent a networked server from having cached & continuing to display it. Or potentially a rogue server which makes everything they have permission to see publicly available.

I'd say its more likely to be user error. The article references oauth and facebook so it seems likely the user clicked through things without reading unless there was an xss vulnerability.

That is patently absurd.

Simply put the US population (or at least the portion that politicians pay attention to) seem unwilling to fund being first.

Nice straw man. No one is claming C02 and global warming have an immediate effect on health (obviously there are thoughts that if the climate shifts a significant amount we might see tropical disease and parasites expand their range but no one is claiming that is now).

Ignoring entirely why the us feels it's courts have jurisdiction at all, any other outcome would have resulted in these countries and their friendly neighbours legislating TLD definitions.

This could reasonably apply to any major car manufacturer going back a decade.