1,147 karma · joined August 22, 2013
1) I can search for a handful of specific terms I remember were on a webpage I didn't bookmark, and I can type them in and find what I'm looking for instead of them being "interpreted" by something trying to be too smart
2) Nobody bothers to send them the same DMCA takedowns that they send to Google, so I can find torrents and things I couldn't otherwise
But on most days, Google is easier to find useful stuff when I don't know specifically what I'm looking for or the exact terms to use.
In an ideal world, I'd have Google default to more of how DuckDuckGo seems to work, with a "fuzzy search" option you can use if needed
"The key point here is our programmers... They’re not capable of understanding a brilliant language... So, the language that we give them has to be easy for them to understand"
760-733-9969
https://en.wikipedia.org/wiki/Mojave_phone_booth
This was also a great read, and the pre-order also included a bunch of goodies including broken glass retrieved from the phone booth
Forgot that we cant message on HN but it doesn't look like your email is in your profile. Feel free to shoot me an email at nick dot price[@]nightowlrecon.org
This project is a great opportunity to learn or expand your skills if any of the stack is interesting to you - a big part of our goal is to help build up the technical skills of anyone who wants to dive in somewhere.
We've got a number of investigators on staff and are starting to get a decent feedback loop with them to iterate on what we're building.
We've also got some unique and useful ideas that haven't been implemented before, and if things go well, we really think this could give a kick-in-the-pants to Maltego and Palantir's offerings, amongst others.
If anyone is interested or wants to know more, please let me know!
Fedora's tool does not automatically report the bugs - it just automates the process of allowing the users to do so if they choose, and handles generating stack traces locally or remotely (configurable) and dealing with core dumps and submitting them if so chosen (again configurable), and tries to tie crashes to existing bug reports if you choose to submit the data to prevent devs from being flooded.
It even has some pretty great functionality to help make sure no private/sensitive data leaks in the report, and lets you go through things line-by-line that based on a default or custom list of keywords that may indicate sensitive data (such as passwd, key, etc.) before you finally choose to submit it.
And it's all done on a case-by-case basis, so for each crash you can choose whether to submit any data or not, in case you're running one app that you'd be concerned about leaking sensitive data versus another.
In many cases it's actually cheaper than buying the bare ICs at their normal price.
Would be pretty interesting if that weren't the case though; quite literally "you are what you eat."
https://www.researchgate.net/publication/251449018_Mitigatin...
One thing to consider though is that our bodies have evolved to eat all sorts of DNA - fragments and full genes - without directly incorporating it into our own genomes.
I'd personally be more concerned about plants expressing new allergenic proteins or that sort of thing, but it seems like there are already some decent methods in use to detect that.
Go already uses libc by default on many platforms. But there are issues - sometimes the libc behaves differently than Go's documented APIs, but this is primarily a documentation issue. Contrariwise, sometimes, Go's native APIs don't behave on systems due to platform-specific implementation bugs.
I think this is a good move overall.