To keep me from advocating an unpopular, but entirely rational, position – all while other people freely misrepresent the First Amendment in response to my comments.
To keep me from advocating an unpopular, but entirely rational, position – all while other people freely misrepresent the First Amendment in response to my comments.
IAAL, and I think you should make up your own mind about what the agreement means. Personally, I think you're over-thinking it, but you shouldn't take my advice, because I don't represent you in this instance. It's a shame that something so simple has to be so dressed up by Apple's legal group in obfuscated language. I also fault Apple for deferring to its outside counsel on these matters. There's nothing stopping them from using plain english that everyone can understand in these agreements. Having said that, I read so many of these things, that I recognize 75% of it as pure "boilerplate" that is for all practical purposes ignored by everyone.
@cooldeal: Nope, I'm dead serious. There's no fundamental human right that entitles you to tell Apple (or any other device maker) what it can and can't sell you.
@recoiledsnake: (for whatever reason, I'm not allowed to reply directly to you)
You're comparing Apple's ecosystem to Earth's.
Apple is a private company that makes products that are sold on the commercial markets. The Earth is something entirely different. If Apple made planets, then yes – they could decide how to manage the atmosphere. That's how business works.
Yes, and never mind that just about everything you take for granted about personal computers was "given" by Apple, too. I find this notion that users are entitled to complete device freedom really annoying.
If you find it so objectionable, go build your own hardware and OS platform. This isn't a matter of human rights because no one is telling you that you can't make your own.
Are you taking the position that only auto-generated passwords can be secure? I'm trying to understand what conclusion to draw from your comment.
My point was that imposing length validations on passwords is not hard. Complexity validation, while more difficult, is also not exactly a novel problem.
I feel like I'm in bizarro-world with all these people telling me that sending a plaintext password via email is more secure than giving users the option to follow an authenticated link to create their own password because...users can't be trusted to choose good passwords?! Really?
A. They don't need to remember any password. They're creating it for the first time.
B. Minimum password length/complexity. It's not hard to do.
I can't believe you're actually arguing that creating a new password is less secure than using an auto-generated password that was sent via email. I hope you are just confused...
And what percentage would – like me – delete their account as soon as you send them a plaintext temp password?
You're living in the past if you think this is an acceptable practice. I don't care how trivial your web service is, if you're throwing my password around willy-nilly, I don't want you.
I wish more apps would get out of their own way and employ standard UIKit. I'm all for experimenting with UI on a new-ish platform like iOS, but the amount of parallel energy expended on checklist UIs is just depressing to me – esp. when the standard Cocoa libraries are more than adequate. There are just so many cases where turning the UI upside down is counterproductive.
Actually, it has nothing to do with ruby. The problem here is that some people use minification tools that rely on semicolons. If that weren't the case, this would be a total non-issue.
Am I the only person who considers use of the word "smart" as a leading indicator of the absence of intelligence? The term is so vague as to be utterly meaningless, and is usually a signal that we're really talking about someone's insecurities, their feelings of inadequacy, or their passive-aggressive megalomania. /psychobabble