Um, in almost no countries is it law that the mobile operator has to know who the customer is. Here, we can just buy a prepay SIM for $10 at the supermarket, put it in the phone, and start calling. No ID needed. Your post is a huge crock of shit.
You're talking about Dropbox, the service that accidentally during a code push made it so that a user's password wasn't needed to get at their Dropbox files, and managed to get an extract from their user database stolen. I don't call that "a proven track record of security and reliability", unless you mean a bad track record.
Yes, it's as good as the "Disable Advertising" checkbox that randomly re-disables itself, and disappears completely if you actually dare to give Slashdot money.
I was definitely not aiming for insightful with that, by the way. Funny, maybe. Unless someone got insightful from a comparison between a schizophrenic and a corporation... hmm. Not so far fetched now I think about it.
Yes, and Linux distros come with fuck all to no support, dubious QA, and a design philosophy that scares the crap out of anyone that actually wants friendly software.
"OEM System Builder Software - Must be preinstalled on a PC and sold to another unrelated party."
And if you read the actual license text (http://oem.microsoft.com/public/sblicense/2008_sb_licenses/fy08_sb_license_english.pdf) it specifically says you must install the software on a customer system, and defines customer system as one you sell.
Actually, there is. It's on the OEM System Builder license, which has to be agreed to in order to purchase OEM media. It specifically says that end users are not eligible to acquire System Builder licenses.
Except they were violating their distribution license doing that. This is about legitimising those sales so that Joe Home-System Builder doesn't have to pay full retail.
Nah, Dev Tools and Office are the divisions rolling in cash. And Mac BU, which is apparently the largest Mac development house in the world (and people say Microsoft and Apple compete...)
System builders aren't supposed to buy retail. System builders are supposed to - and do - buy OEM System Builder licenses. People building their own PC were supposed to use retail licenses, but instead were buying OEM from resellers who were violating their distribution agreement (they would routinely sell OEM Windows with a mouse, despite the fact that only a motherboard qualifies as a component with which you could bundle OEM Windows).
And if a human were composed of multiple distinct entities, they could do that too! In fact, courts routinely allow this defense, called "Insanity". And the human can escape punishment also by going into therapy for rehabilitation - and for bonus points receives sympathy rather than condemnation from the general public for the original heinous action!
You missed two Microsoft-related items in the "fails to account for" list. These are required per the checklist protocol. The following would work:
Specifically, your plan fails to account for
(X) Existing court decisions protecting the very activity you want to restrict (X) Scalability (X) Extreme opportunity for mischief when abused (X) Armies of trojan-riddled Windows boxes connected to the internet (X) Technically illiterate politicians (X) Stupidity on the part of some people who do business over the Internet (X) Bing
Hamachi was Acquired, LogMeIn was built. The whole 5.0.0.0 mess is because Applied Networking decided they didn't want to conflict with potential internal IP ranges, so decided to conflict with an entire/8 on the internet instead. Although LogMeIn are the ones that decided to block Vietnam.
Slashdot Mirror
Um, in almost no countries is it law that the mobile operator has to know who the customer is. Here, we can just buy a prepay SIM for $10 at the supermarket, put it in the phone, and start calling. No ID needed. Your post is a huge crock of shit.
You're talking about Dropbox, the service that accidentally during a code push made it so that a user's password wasn't needed to get at their Dropbox files, and managed to get an extract from their user database stolen. I don't call that "a proven track record of security and reliability", unless you mean a bad track record.
Ah, that certainly makes sense then. Actually making copies would indeed require a license and explain the crushing.
No. Psystar modified kernel extensions and a few other pieces of software. They also broke the EULA by selling machines with OSX pre installed.
The EULA only applies to End Users, hence the EU part before the LA. It should not have even applied to them except insofar as modifying the software.
It's not illegal to modify osx and it's not illegal to sell a Hackintosh, it is illegal to make your entire business model selling hackintoshes.
These two lines are mutually exclusive, and fundamentally incompatible.
Yes, it's as good as the "Disable Advertising" checkbox that randomly re-disables itself, and disappears completely if you actually dare to give Slashdot money.
It's almost the same for MSDN though (only 5 keys). Your best bet if you work for an enterprise which does evals of hardware is probably a MAK.
Subscribers can untick a box to remove the asterisk indicating that they subscribe.
I was definitely not aiming for insightful with that, by the way. Funny, maybe. Unless someone got insightful from a comparison between a schizophrenic and a corporation... hmm. Not so far fetched now I think about it.
Yes, and Linux distros come with fuck all to no support, dubious QA, and a design philosophy that scares the crap out of anyone that actually wants friendly software.
They don't provide you even the tiniest iota of support if you have an OEM license. Never underestimate the benefit to not having to have any support.
Zero Support.
Technet is probably closer. It's unlimited use evaluation licenses basically. MSDN is for developers, Technet for sysadmins.
No, whoever said that is right and YOU are wrong.
See, http://www.microsoft.com/oem/en/licensing/sblicensing/Pages/licensing_for_hobbyists.aspx#fbid=pku8zxVMZJP
"OEM System Builder Software - Must be preinstalled on a PC and sold to another unrelated party."
And if you read the actual license text (http://oem.microsoft.com/public/sblicense/2008_sb_licenses/fy08_sb_license_english.pdf) it specifically says you must install the software on a customer system, and defines customer system as one you sell.
Not illegal, but it does violate the system builder agreement.
See, for example http://www.microsoft.com/oem/en/licensing/sblicensing/Pages/licensing_for_hobbyists.aspx#fbid=pku8zxVMZJP
"OEM System Builder Software - Must be preinstalled on a PC and sold to another unrelated party."
And if you read the actual license text (http://oem.microsoft.com/public/sblicense/2008_sb_licenses/fy08_sb_license_english.pdf) it specifically says you must install the software on a customer system, and defines customer system as one you sell.
Actually, there is. It's on the OEM System Builder license, which has to be agreed to in order to purchase OEM media. It specifically says that end users are not eligible to acquire System Builder licenses.
Except they were violating their distribution license doing that. This is about legitimising those sales so that Joe Home-System Builder doesn't have to pay full retail.
Nah, Dev Tools and Office are the divisions rolling in cash. And Mac BU, which is apparently the largest Mac development house in the world (and people say Microsoft and Apple compete...)
System builders aren't supposed to buy retail. System builders are supposed to - and do - buy OEM System Builder licenses. People building their own PC were supposed to use retail licenses, but instead were buying OEM from resellers who were violating their distribution agreement (they would routinely sell OEM Windows with a mouse, despite the fact that only a motherboard qualifies as a component with which you could bundle OEM Windows).
Not if they're contractors!
And if a human were composed of multiple distinct entities, they could do that too! In fact, courts routinely allow this defense, called "Insanity". And the human can escape punishment also by going into therapy for rehabilitation - and for bonus points receives sympathy rather than condemnation from the general public for the original heinous action!
Well for us the employee is actually easier to find if they're in the hospital, since that's the office!
You missed two Microsoft-related items in the "fails to account for" list. These are required per the checklist protocol. The following would work:
Specifically, your plan fails to account for
(X) Existing court decisions protecting the very activity you want to restrict
(X) Scalability
(X) Extreme opportunity for mischief when abused
(X) Armies of trojan-riddled Windows boxes connected to the internet
(X) Technically illiterate politicians
(X) Stupidity on the part of some people who do business over the Internet
(X) Bing
Until you get a UAC prompt. Then you're screwed.
Hamachi was Acquired, LogMeIn was built. The whole 5.0.0.0 mess is because Applied Networking decided they didn't want to conflict with potential internal IP ranges, so decided to conflict with an entire /8 on the internet instead. Although LogMeIn are the ones that decided to block Vietnam.
TeamViewer's paid solutions are very expensive, so that's probably why they can afford to have a free version.