Falsehoods Programmers Believe About Families
shkspr.mobi
shkspr.mobi
Because "Family" is a way to group some people together to sort-of share an account, not intended to cover every single situation someone might use the term for.
This is a pretty ridiculous article. If you can't join a new "Family" for a year, that doesn't mean Google doesn't recognize your living situation, it just means Google doesn't feel like extending their sharing whatnot to you.
The intent is pretty clear - I'm sure there would be a rather suspicious number of "15 person families" that interlock, span 4 different countries, etc. etc. the minute Google relaxed their ToS. And I can't help but wonder how many really large families genuinely have members spanning an age range where the oldest kid is still at home and little Timmy actually needs his own Google account.
Just toss "family plan" into Google and look at the results that come up. It's a really common term and they pretty much all have arbitrary limits like this, because "family plan" means "plan that might be more suitable for families" not "plan that suits every single family ever."
It's common with other words too. Happy hour isn't limited to happy people, nor is it guaranteed to produce happiness. Kids meals have an arbitrary age cutoff even though "kid" is often more varied. Express lanes are sometimes slower than the regular ones. Hacker News is rarely about cutting things with rough or heavy blows, and often not about news.
You ask, "whose problem is that?" My answer would be, nobody's, because there isn't a problem for anyone to have in the first place.
I doubt the programmers had any say in what the restrictions would in the first place.
If I had to hazard a guess the arbitrary nature of these rules sound like they come from someone in the legal department and was established as part of contract negotiations for the price of the content.
The only limit should be "only one device can consume the content at a time", nothing more or less.
Contractual. Not a moral issue, not an ethical issue, just that Google doesn't want to deal with people that way.
One can fruitfully discuss the second-order issues of excessively-strong DRM but I'd consider that, well, a second-order issue. The first-order issue of Google not wanting to contract with an amorphous group of "family", a word that has basically no agreed-upon meaning (even if there is a legal one it won't match everybody's idea) isn't that horrifying.
And, even if they did content owners would set pricing that would be prohibitive for the first copy if it was likely that it could be purchased by a giant sharing community.
You can't send a DVD or a book instantaneously around the world, but you can with a digital copy. This means there is a lower bound to how fast you can share a physical copy, so the practical effect of the ability to share a book has a limit. There is no such limit with digital goods.
Second, do you really want to go down the route required to ensure that 'only one device can consume the content at a time'? You can only ensure that by requiring a constant internet connection, to verify that you are the only one consuming the content at a time (or at least require you to go online to 'check it back in' to allow another device to use it)
Then expand my "1 device at a time" limit to "each media can only be used by one device, after use it’s locked to that device for 24h".
In 24h I can ship a DVD from any place to any other place on the world with DHL.
One of the most important policies of the digital market is that it should be a strict superset of the real market, allowing 1:1 all things the physical world does, and more.
If the digital market has additional restrictions, then those have to be removed, no matter how.
The EU already requires by law that you can lend out a product you own, physical or digital, resell it, or refund it. Unless companies like Google allow these things in the same (or a more lenient) way as in the physical world by themselves, there will be more laws enforcing this.
There's some amount of allowed sharing that (they believe) is optimal for their revenue, and apparently that's greater than zero, so that's why they have introduced this "Family Library" concept. They could have chosen not to do it at all, that's a valid setting too.
I'm sure that they have considered "only one device can consume the content at a time" but decided that it's not the best option, especially for the sales of "long tail" older content - your own mention that "Groups which share newspapers, DVDs, books, etc between them, often counting hundreds of members" exist is a very good answer about why allowing groups without limits could be a bad decision.
Fully meeting arbitrary definitions of "family" isn't the goal of such policy; the goal is to balance ease of use (i.e. match the general expectations of target audience) with limiting exploits to something that doesn't have a big impact on revenue. The bottom line doesn't care if Bob is your roommate or bedmate or what family relationship you (don't) have; but it does care about how convenient it is for random Bobs or distant family members to join your group instead of paying for another copy.
It's worth to look at the alternatives you have - a roommate that's not a family member is anyway likely to watch your copy, so allowing them to join a group isn't a lost sale; but an overseas adult child is likely to buy stuff on their own, therefore excluding them is a feature, not a bug.
So I think the family number limit makes sense.
I dated a woman with Russian ancestry in NYC, she used her family's Amazon Prime account. Her parents weren't the primary account holder either-- the account had nearly 200 addresses in it when you go to the "where do you want to ship this?" option. The extended family and "friends of the family" were all on it. It worked great--- except everyone can see the order history. So there was some family drama when her younger sister ordered lingerie to her boyfriend's apartment, using that Prime account.
Be 18 or older -> Minors can't enter into contracts to buy things.
Live in the same country -> Copyright is different in different countries. Media X may not be licensed for location Y.
Totally not true in some (many?) jurisdictions.
http://www.nolo.com/legal-encyclopedia/lack-capacity-to-cont...
A number of people on Twitter have taken the title literally. "This is about managers and lawyers!" they protest. But, of course!
All of the "Falsehoods" memes - including the original - are a shorthand for "Constraints placed upon a complex system by a mixture of ignorance, apathy, business requirements, or other legal constraints".
- "But, yo, how are we gonna make money?"
- "Hummm, advertising, maybe?"
See, they've been down that road, we've been down that road. When you grow up you deal with the so called "crap".
Perhaps the solution is to provide two options: either (1) the common (Western?) given|surname structure or (2) an Nx2 matrix in which the key is what the name part is called on legal documents in the region and the value is the corresponding name part.
An example…
Full name: "Hajji Halef Omar Ben Hajji Abul Abbas Ibn Hajji Dawud al-Gossarah"
Title: Hajji
Ism: Halef Omar
Nasab: Hajji Abul Abbas
Nasab: Hajji Dawud
Nisbah: al-Gossarah
A database for the keys can be maintained and suggestions can be offered to the user at submission time in order to keep things tidy. Additionally, per-region templates can be maintained in order to make the Nx2 approach less burdensome.
Users submitting names under #2 would be additionally required to select two name parts so that their name can be shoehorned into the Western model.
Continuing with our example…
Given Name: Halef Omar
Surname: al-Gossarah
(Here's a reward for putting up with my absurd example: https://www.youtube.com/watch?v=o3V-9Az5FUs)
And of course, nobody enjoys using a product/service and then thinks, wow, they must have amazing programmers!