Maybe more websites need to enforce strong password rules on their users. I know that plenty of sites either read the password entered or check the hash and reject it if it doesn't meet certain criteria. Ideally, end users would come up with secure passwords on their own, but since they can't, administrators need to do some prodding.
The submitter can be bothered to capture some data and submit a link to such to slashdot for commentary, comparing apple's actions to Microsofts (but not Ubuntu's, but that's a different story), but can't be bothered to summarize the data at the very least, even better would be to actually write an article explaining what they found. I'm not going to spend hours clicking through git to find out what the submitter is complaining about, and i doubt that most anyone commenting on this article will have done so either.
"So ultimately OS X is the only desktop UNIX out there. If OS X runs it, then it works on Unix. If it doesn't work on Linux or BSD, then the OS X should be considered the correct behavior. Keep in mind that POSIX does not define any GUI behavior."
I'd change that around...
If it works on Unix, then it will work on OS X. But just because something works on OS X does not mean that it'll work on any other Unix... you know, Cocoa libraries, Aqua UI, etc
Don't quote me one it, or maybe, yes you can. But BSD is real Unix, whereas Linux is posix compliant/compatible, but not a "real" unix.
Not that it really matters, it's all just semantics at this point, I think...
what would be cool is a combo unit... storage in the screen, along with an arm processor and its own gig of ram, along with intel processor in the body along with they keyboard. Attach the screen, and its a Macbook Air. Remove the screen, and you've got yourself a full featured iPad. And no matter which way you take the device, all your docs are stored locally, always accessible... I'd buy that, at least, so long as it was priced a bit less than the sum of a Macbook Air and iPad.
Even with Windows, old version, not sure about the current, but you could customize interface elements to your hearts content in the control panel, but any changes too far from the standard would basically wreck the interface. It'd still function, but none of the elements would fit longer.
So i can understand apple locking down their interface somewhat, but i do agree that perhaps they took it a little too far. Changing a font from helvetica to garamond, for instance, shouldn't break anything too badly...
Oh, how i wish i had mod points for you, Mr. Anonymous Coward....:)
By LESS CAPITALISTIC, you mean less entitlements, fewer safety nets, less government regulation and oversight, lower taxes on the most able to pay, and an expansion of the richests' ability to advertise for their own ends in elections, correct?
I had real problems believing the story til I read that. I was thinking "can't be tru - Rumsfeld and Cheney would have had a field day with that", on,y to read the link and go "oh.... That's why!"
I'm pretty sure its illegal to record a phone call without the other parties approval in the United States. I wonder if they've taken this into account? Like, when person A initiates recording, does it just record or does it ask for confirmation from person B?
were past the stage of "don't write down your passwords". Too many sites, too many passwords... Personally, I use pwSafe (a mac and iOS version of Schneiers password safe), but i know plenty of people who keep notebooks hidden with their passwords all written down. Better that than use a single password everywhere.
Whats the alternative, though?
You can object to the notion all you want, but as far as your tax return goes, that's exactly how you have to treat transactions in Bitcoins, as if you sold the Bitcoins for dollars at the moment of purchase.
FIFO is just the default most brokerages use. You can also (usually) choose to use LIFO, or even specific lot selection. As far as I know, you can only use "Average Cost" with Mutual Funds, though.
Yes, it's taxed like any other investment asset.
The issue is that, if you go ahead and use it as a "currency", each transaction becomes a taxable event. Say you buy bitcoins when they're worth $500 each. You buy a coffee when they're down to $490, get groceries when they're at $600, buy more Bitcoins when they're worth $575 (new tax lot), then buy a Dell computer when they're at $375, each of these transactions is a separate item on your Schedule D.
For people who have them, the best 'solution' from a tax compliance stand point (not that I'm an accountant or anything, nor that many Bitcoiners seem particularly concerned about taxes), is to hold your Bitcoins and then convert them when you know you're going to be making some purchases (i.e., you know you're going to buy 3 cups of coffee and a computer that day, so you sell $450 worth of Bitcoins and make each purchase with cash). That way your Schedule D will at least be slightly more manageable (1 entry for that days activity rather than 4 distinct entries).