1,230 karma · joined April 30, 2009
And aggregation is not a service that would be required anymore if the shops could just go direct to Shimano, SRAM, Fox, Maxxis and DT-swiss (etc). That aggregation can be performed by the bike shop itself via a B2B solution.
That insurance is likely to get a lot more expensive unless Netflix and the agency can come to an amicable resolution with the OP.
I don't think there is any value in looking at this blog post and making any conclusions about which editor and/or scripting language to learn next. You might go interview at a .net shop and get the opposite result from the one that you wanted.
Disclaimer: I personally match their preferred technologies very closely, but work with some really smart people that write C#/F# in VSCode.
>>But why not have an even safer tablesaw? Because I don't want to get complacent around one tool and have that feeling linger when I go use the next tool. They are all dangerous and all need to be treated with respect. Unless there is a way to make them all safe (there isn't), it doesn't make sense to me to have one safe one.
This argument is very irresponsible. Disclosure: I am a happy saw-stop owner who also has a large collection of POTENTIALLY very dangerous tools (gas-welding, milling machines, routers both CNC and otherwise, metal forming, etc).First, every tool that is safer reduces your total risk. Saying that unless all tools are safe, none are, is nonsense.
Second, I know somebody that got caught in a drill press, and I can say from experience that you are very lucky that you only lost some hair. I find it odd that you argue against safety measures in the same paragraph where you note how you took a risk that could literally have lobotomized you.
Finally, safety measures aren't only about you. Does your wife ever use your tools? Is she OK with those risks? Do you have kids (I know a dude locally who got his hand into a planer when he was a _young_ child. He's surprisingly dextrous after being amputated around the first knuckle on every finger on his right hand). Not everybody understands the risks like you do, and it's hard for them to make an informed decisions when they learn to use those tools without some kind of industry guidance.
https://github.com/kiteco/kite-installer/commit/c52c5daa672c...
Taking over the minmap autocompletion projects and adding these features still feels a bit sleazy, but the installer was honest about how it worked.
If the desktop client is failing, then he's not getting what is promised "on the box" (or in the feature set advertised on google.com).
They sell that client pretty hard btw: https://support.google.com/a/answer/2490101?hl=en
To use the full power of Google Drive, you should install Google Drive for Mac/PC, a desktop sync client. This synchronizes any or all your files to Google Drive on the web, making them available anywhere, at any time, on any device. It also provides secure, cloud-based storage for your files.
resolve_renderer_module(user_agent.os)
where the osx/Windows ones are already loaded in RAM, but it has to try (and fail) to load the linux one every time somebody tries.
This is classic Hanlon's razor stuff.
It is not only common, but NORMAL for hackers to have unknown exploits before the vendor is aware of them. Where do you think 0-days come from? In fact, there is an annual competition to break these devices with previously unknown attacks at CanSecWest.
Example: http://9to5mac.com/2014/11/13/iphone-5s-samsung-galaxy-s5-ne...
Exactly, although we wouldn't be having this discussion because he wouldn't have had the platform to transmit his thoughts on the matter.
Imagine that you're working on some project and you find one of those forks with no GPLv3 attached (or worse, some other license that is more permissive). You integrate it, publish, and then find out that your project is in copyright violation.
I'd rather see a takedown induce an easily remediated repo change, than a big legal PITA down the road. It's not like he took his repo down, nor any of the forks that kept the license. He just DMCA'd the ones that stripped the license files.
ref: https://jonathan.porta.codes/2015/07/30/windows-10-seems-to-...
Also, it seems that Win10 ignores some of these settings: https://www.reddit.com/r/Windows10/comments/3gm1e3/what_wind...
It's fortunate that newer platforms seem to be immune (see https://security-center.intel.com/advisory.aspx?intelid=INTE... ), but remediation after exploit via total hardware replacement would _suck_ for anybody with servers just a couple of years old.
I too eat meat, drink beer, and talk about the same topics. You'll find that is true of most "hackers" in the bay area too. The term hacker is used more often as shorthand to describe somebody who is into technology without getting into the details (software&hardware&ux).
I have seen precisely one person ever describe themselves as a rockstar, and we rejected his job application for plagiarizing his code samples. Nobody in the real world does this, and you're unlikely to get force-fed yoga, lifehacking, etc.
There are still things that weird me out about the bay area, but overall I really enjoy my time there. I encourage you to check out some tech meetups.
Oh. And Noisebridge and it's mailing list aren't representative of the larger geek community in SFO either, just saying ;)
Budgets are finite. That's a fact of life. The trick is balancing the risks and hardening the important things so that, on the balance, you have the most security possible for that budget.
Not spending as much money hardening the (hypothetical) legacy DB with a noncritical data of some sort, so that you have more budget to harden the financials database; that is the right decision.
Of course, it doesn't look like that balance was struck effectively very often at Sony Pictures, but the theory is sound :)
http://www.freepatentsonline.com/y2014/0121813.html <- I've been filling with urethane glue for a while now, as a side note,
http://www.freepatentsonline.com/20140120196.pdf <- http://www.thingiverse.com/thing:12320
http://www.freepatentsonline.com/y2014/0117585.html <- everything from lexmark/HP/etc. Oh, and a workaround for existing implementations already exists: http://hackaday.com/2013/04/26/cube-3d-printer-hack-lets-you...
Reading over these, they really look like a landgrab on ideas that have been floating around in the reprap forums for a while now.
http://thr3ads.net/gluster-users/2011/06/480298-Enomaly-user...
This bug (and others) would happen when moving files and/or folders over top of existing ones, ie:
mkdir -p foo/bar/baz && \
mkdir -p foo/bar/tmp && \
touch foo/bar/baz/file foo/bar/tmp/file && \
mv foo/bar/tmp/file foo/bar/baz/ && \
rm -rf foo/bar/tmp
This was a method to replace an existing lockfile. Mercurial uses some similar code. The expected behavior would be that foo/bar/tmp/file replaced /foo/bar/baz/file. Instead, the outcome was that there was a race in Gluster where it got confused about which version of 'file' was correct, and it would end up with a split brain between the two nodes. This would be exacerbated by a node failure, but didn't always require one. Heavy load seemed to make the failure more likely. We couldn't replicate the same bug moving files in the same folder, it was the subfolders in the same gluster fs that seemed to cause the issue. The frustrating part was how gluster pointed fingers at the file operation being incompatible, despite advertising a posix compatible filesystem. Apparently the bug is fixed, but we moved off gluster, never to return.Also, filesystems are hard, I get it, so no hard feelings :)
It'll be interesting to see how this situation shakes out for this auditor, but I suspect they'll keep ticking along just fine.
Besides, this isn't even low hanging fruit. If you want to really find some terrifying github contents, try to think of a library that is used to access the TTY, say to enter passphrases for ssh/telnet/mount/sudo/etc. in a PRODUCTION environment. Then think how it's api would be used, and search for that. Example below: using expect to enter passphrases:
Example:
https://github.com/search?q=+expect+send+root+ssh&type=Code&...
There is a ton of low hanging fruit out there.
Also, the ADA initiative doesn't really have a choice here either. Either draw a hard line, or look like they aren't able set the same standards that they ask from others.
Finally, if the investigation at Github turned up real mistakes of judgement, why weren't they itemized? We are left guessing what the investigator found. Github has that report, yet they are being evasive about it's contents. Air that stuff out. Stating that the allegations are unfounded at the same time as revealing that undisclosed mistakes in judgement occurred, combined with pushing out a founder: doesn't smell right.