I actually just bought all the wood to build the frame and I'll hopefully be doing next weekend.
368 karma · joined November 26, 2013
I actually just bought all the wood to build the frame and I'll hopefully be doing next weekend.
[1] http://www.muppetlabs.com/~breadbox/software/tiny/teensy.htm...
> We find, for example, that after their first scan error, drives are 39 times more likely to fail within 60 days than drives with no such errors.
So basically, if you are getting SMART errors, you should make sure that data is backed up (if it isn't already).
Another interesting section is:
> Out of all failed drives, over 56% of them have no count in any of the four strong SMART signals, namely scan errors, reallocation count, offline reallocation, and probational count. In other words, models based only on those signals can never predict more than half of the failed drives.
So, while monitoring SMART errors is a good indicator if your drive is going to fail, it's hardly failsafe, and chances are you drive will fail without any notice. SMART stats are interesting, but not the ideal measure of the health of a disk.
[1] http://static.googleusercontent.com/media/research.google.co...
That is more in depth, but is a lot more math heavy, which the author specifically states they are trying to avoid.
[1] http://www.ebay.com/itm/Second-Hard-Drive-2nd-HDD-SSD-Caddy-...
That was my suspicion from the start, security questions tend to be the easiest way to compromise accounts since finding someone's mother's maiden name isn't hard to do anymore.
I work for a company that does this, [Hitachi-ID](http://hitachi-id.com/), on a corporate level. We have a piece of software called Password Manager that captures end-user password changes and synchronizes it between all their different accounts. Alternatively, we have another tool called Privileged Access Manager that randomizes all your server passwords on a schedule, and allows people to check them out to allow for better auditing and security (through manual checkout authorization).
The problem with doing this on such a large scale is that everyone has a different way to do password resets. We integrate with a zillion different target systems to perform password resets, but those are primarily corporate applications. Doing this for websites would be near impossible because there are so many different ways to do password resets and many are "home rolled", so you'd have to find a way to reliably capture and perform those password resets, which isn't trivial.
The web has so much freedom, but it makes stuff like password security harder because that much freedom exists.
Not to mention the computational and storage cost.
Programs like this are there to show that an industry isn't specifically for only men or women, and allow girls to make the choice to code, even if they previously hadn't thought of it as an option.
> Register your app to handle voice actions, like "Ok Google, take a note."
I think this is what most interests me. Hopefully we won't be locked into Google's pre-defined tasks and developers can start working on their own voice actions.
https://itunes.apple.com/us/app/jetpack-kitty/id567551748?mt...