skysight-inc/HackerNews huggingface dataset:
The work that DARPA does is incredible and we should be proud, as a country, that we pursue transformational research. One of the big weaknesses of the private sector is that there are few opportunities to pursue high-risk high-reward research and research that must be done on long timelines.

The stuff DARPA funds is fundamentally important and has an incredible track record.

That said, their primary customer is the DoD which has demands for technology that is sometimes rather creepy. Without going too far down that route and forcing a tangent on the thread I'll just plug here that technology is power and that power can be used for good and evil, for noble and ignoble and for personal or public gain. We need to cheer on DARPA for its development of technology and keep its customers accountable for how it applies that technology.
To clarify, I'm suggesting that we need to walk before we can run. I absolutely agree that many individuals without a degree far surpass companies' hiring needs, but our initial focus is entirely on providing a diverse pipeline of talented candidates who fit the criteria our partners are seeking. As we continue to demonstrate this value, it would be exciting to find ourselves in a position to influence the traditional pipelines that companies turn to for talent.
I think it's interesting that anyone would use the iMore web site. I looked at it, and if I had accidentally stumbled upon it, I would immediately run a way. When a web-site response so poorly, I just feel like I can spend my time else-where. Does anyone disagree? If so, what would cause you to go to that site?
"The pool of applicants for any given job is largely a function of the people who've already been hired."

That makes no sense. It seems far more likely you've just got correlation effects going on; a given physical office has a certain local distributing of people.

And this is part of the reason I'm trying to keep to the legal aspects. Any new pool of applicants can only broaden the "diversity", but that doesn't mean you could use the complementary service without getting into serious legal trouble.

Preferences are one thing, but this appears to be out-and-out racially discriminatory. Even as part of a recruiting diet it seems legally dangerous, because as I tried to show with my link, there are limits to the preferences that can be displayed.
Updating freeimage on homebrew
Also, it just so happens that the people working on NeoVim are currently porting all IO to libuv (the cross-platform library mentioned in the article).

https://github.com/neovim/neovim#whats-being-worked-on-now
I am currently experimenting with sentiment analysis using Python scikit-learn and NLTK. Working on a project that tries to predict if a user rated a business positively or negatively based on his review comment. I have access to only the 160 characters of the review (not the full text) along with the rating given by the user. With 10K samples of reviews and their ratings, I am currently at 70% accuracy in predicting if a review is positive or negative.
I'd like to know the answer to that question.

But also, this one:

s/an arbitrary/each/
Announcing Our Matching Fund Donation to Chelsea Manning's Legal Defense
Sure, but how long is this solution available and in how many years do you think it will be deprecated? Getting a bit offtopic though.
[The idea that the pool of applicants for any given job is largely a function of the people who've already been hired] makes no sense.

You don't seem to be familiar with how hiring works.

Referrals are a thing, for instance. Job openings tend to get shared within the networks of employees.

I'm honestly amazed that this is a point of debate.
>Either you get it, or you don't.

Yes, I like binary logic.

Comments about the parent's author vs. comments about the commitment level of the people behind the parent's content's focused project (which is therefore a comment about the author's of Keybase)

I guess there is a distinction there (or at least I just named some distinction), but I'm not really sure why one was judged more acceptable than the other.

Edit: Ok, I guess you (or some anonymous down-modder) want more.

> and this entire sub-thread have nothing whatsoever to do with the structure of funding

This is just plain false. You lampooned my scenario in your first sentence into this sub-thread.
As most people here point out, hard to say without more details. Here's the simplest practical advice I can offer: if you have any options vested and have not exercised, buy them immediately so that you become a voting shareholder. It will cost some $$ that you may never see back (tho hopefully very little, since angel-stage), but it will buy you some leverage. Even if it's a fraction of a percent, as a shareholder you can vote on the transaction and even though the founders / angels will have a majority and be able to push the deal through regardless, dissenting shareholders are always a major concern for buyer/seller in M&A, and so you can have some impact on the deal.

Most deals like this will be set-up to have key employees and founders work for buyer at least 18-24 months, and while I understand you don't want to do this the bottom line is in deals like this, developers like you, and your willingness to work on product integration, ARE the value so if you're unwilling to do that then there may be no deal, but more likely you just won't be able to realize very much of the deal's value since the buyer will set it up to make sure only people who stick around are compensated. Not much you can really do about that.

In fact, if you want to be machiavellian about it all, one play would be to make your founders and buyer believe that you REALLY wanted to work at buyer so that buyer got comfortable with putting more of the consideration upfront and not-tied to vesting - this would be somewhat dishonest IMO but people do it (I've seen it happen for $200M+ deals...). Contra, if you expose that you don't really want to work with buyer, they will certainly tie any consideration to vesting/earnout.

Best advice is be honest about what you want and ask for it (really the only people who can answer the rest of your questions are the founders and buyer - these are exactly the questions that get hammered out in deal terms), but also be empathetic and hear out why others might have different priorities - ultimately a deal like this is one team being absorbed by another team, all made out of people with divergent interests, so you just have to make compromises.
I really dislike the code review witch hunts you see on HN (or anywhere). On one side of the coin you have startups that merely want to get something thrown together with duct tape, working and ship so they can refactor later and clean things up. On the other hand you have people writing blogs posts to humble brag their code reading and blogging ability.

No one knows the circumstances that created this original code. The developer may have been working on 10 projects and threw something together just so it'd work.

If it ain't broke....
See here:
https://github.com/neovim/neovim/commit/4528046
They are gifs. I used Open Broadcaster Software to record the videos and then used ezgif.com to convert those videos into gifs.
But the code works. It supports lots of platforms through choice. Yes, you could make the code prettier if you dropped some platforms. Yes, you could refactor it to use some abstracting libraries that now exist. But the code works. If you rewrote the code, the best result you could end up with is the same functionality that still works. All other possible results are bad. There is nothing to be gained.
A perfectly valid, if somewhat ominous, point...
Yes.

For those readers who are interested, they assign the primary colors to various important parts of the spectrum representing various elements.

Watched a wonderful set of lectures from The Great Courses that explains this. Highly recommended for laymen who are interested in astronomy.

http://www.thegreatcourses.com/courses/understanding-the-uni...
I got kinda sucked into this situation a long time ago..

You don't own the product and your stock is now worthless. Being unshakably loyal to a product you don't own and a company you don't own is undermining your negotiating power and is not in your best interest. Letting go of your attachments and making it clear you are comfortable with walking away is very important.

If the product is all in your head and would take a small army of code monkeys to maintain or expand otherwise, then you actually may be the only true salable asset the company has. Even though the negotiation is technically around the product, it's you who would be up on the auction block. If you walk away, they have nothing. That's your bargaining chip.

However, if they haven't already discussed a specific buyer who's on deck, I'd be skeptical that the business is even salable. Don't jump the gun on assuming they'll sell it as an acquihire, you may very well end up without a job very soon. I'd go out and start interviewing, it's a fallback if the sale never materializes and leverage at the negotiation table if it does.

Also the founders at best might get an employment offer from the acquirer, if they're lucky. You as the product mastermind however may be able to negotiate with the buyer for all kinds of things like extra cash, a good title, a 3 day workweek etc..
Modal and tooltip/popover are the components that forced me to add react-bootstrap to my project (I didn't want to build those on my own.) Really looking forward to trying out Belle once those land.
PriceTea – Simple Amazon Price Guides
"As a person who grew up in a place where discrimination based on gender/age/race was not really a thing, this strikes me as insane!"

It would behoove you to first try to empathize with those who did live in these kinds of places & learn about the history of education & discrimination in America. Then you may have some better perspective on why there are systemic reasons for why the diversity numbers for technology companies is so low (and maybe you would get an idea of why thats even important).
Not clear that the value of closing this outweighs the value of being able to track exploits.

I assume that the Android rootkit mentioned uses known exploits- the companies not pushing out fixes bear some responsibility as well.
The point of using an adblocker is that in many cases it's really hard to ignore an online ad, seeing as there's often a noticeable performance hit (in terms of both computing and connectivity) and seeing as how such ads are in a downward spiral as they aggressively try to outdo one another.

On that note, AdBlock Plus gets a lot of heat for having an "acceptable ads" list, and I never understood why. I don't mind advertising, either, so long as it doesn't degrade my user experience, and that's what ABP has been shooting for.
I was in college when the object-oriented COBOL standard was released -- my software engineering professor at the time mentioned it in class one day and made the (obvious) joke that it should have been called "ADD 1 TO COBOL."
Playing with Ubuntu's New Fan Container Networking Project
I agree with you. Not all of this can be refactored into separate functions, but the parts that can't can be refactored to be much cleaner after you remove the #ifdef's made unneeded by the functions.

Generally speaking, a lot of the cross-platform stuff in the Linux Kernel is handed this way, and done correctly there shouldn't be any over-head.
Sounds familiar? cough Hacking Team cough
Interesting points. The below is a friendly disagreement from someone passingly interested in this field.

> First, people should have multiple keys/identities by default

I feel like you can do this already, no? Just create different Keybase accounts for each identity. I don't understand how having a single keypair prevents you from managing your contact groups however you like. They seem like orthogonal problems to me.

> Second, matching a name with social media is the wrong way to lookup others. It only works if people put enough personally identifiable information (PII) on their social media accounts

Key verification is the problem in crypto. Like it or not, many people already put tons of PII online. It's a perfectly valid way to verify lots and lots of people. Perhaps it doesn't work for everybody, but it's clear that keychains don't work. This is a different strategy to solve the verification problem, and I think it's got legs.

> Third, leaving people to manage their own private keys is worse for security than having them managed by others.

I understand your point here, but I disagree. Given all the server hacking going on these days, I'd much rather not have a single point of failure. Or several large points of failure, in the case of your distributed system. The odds of someone hacking keybase.io or keyexchange.google.com seem much higher than the odds of someone attacking my phone or my desktop.

I think it's a mistake that keybase allows uploading and storing private keys.

> I think the winning solution will be: a distributed

Your idea doesn't seem to solve the verification problem. Keybase's strength is that in order to subsume someone's identify, you have to hack several of their accounts. That's much more difficult than hacking a single keyserver. How do you verify that the key I get when I search your crypto-DNS system for irq-1 actually belongs to you?
You have a point about the clickbaity look of the site.

The editor, Rene Ritchie, has a following. He was relatively early to iPhone punditry, and there is a perception that his opinions are well-founded.
I wonder why didn't the vim folks write the abstracting library?
I don't see the point here. The majority of OS hackers are hobbyists to begin with, and learning should be the top priority in any event. Learning for the sake of being employed as a kernel hacker sounds backwards and an unhealthy approach. You demonstrate your skills and then get hired or apply for a job after the fact.

Besides, it's not like you can't be a Linux sysadmin/programmer in your day job and hack on more novel OS as your hobby.

For example, Al Viro was an ex-Plan 9 hacker who later became a full-time Linux guru.

The thing is that once you've been involved in truly different OS architectures, migrating to a relatively boring Unix monolith like Linux isn't all that hard. Besides, Unix and Linux are so widespread there's little chance you won't be using them in some form throughout.

As for architectural interest, I can see a case being made for Plan 9 or unikernels, but most other kernels are pretty similar.

Sorry, but this is a plain falsehood.
I wrote a small snippet to share cache (particularly session) between a php webapp and rails using Dalli long back. It might be completely broken by now, but worked brilliantly back then.

it was based roughly on this https://gist.github.com/watsonbox/3170415
A slight nit-pick, though I was going to say the exact same thing - `|| 0`. If you do `|| 1` the compiler's going to optimize the entire 'or' expression out ;)

I was thinking that using `0` would cause a problem when you select none of those compilation options, but then I realize the code won't even compile if you don't select at-least one (You get empty parenthesis fallowing the '&&' in the 'if' statement), so it doesn't seem like a big deal.
>There is nothing to be gained.

What about easier extensibility? Not many are going to want to look at that code, let alone try to add some additional functionality to it.
eBay is the largest common stocks owner in MercadoLibre
Do you swap projects, or do you move on from DARPA entirely?
3-5 people sounds like a pretty normal acquihire. If it's a distressed sale, I doubt the buyer is going to care much about IP. It's going to be all about hiring a functional team. The product is just proof that you guys are functional.
From my personal experience (dating back to the first .com bubble burst) principal developers are the part of the product. I worked for a startup that ran out of money (all 10+ mil of it) and was actively selling itself to anyone who might be interested. They brought in an interim CEO who was experienced specifically in this sort of wind-downs. They first trimmed all non-techies, then support, then sysadmins and then moved on to the developers. In the end the only people who remained in the company were the founders and two senior devs, me included. For 3 months we just showed up for work at 10, left at 4, collected the paycheck and worked on our own projects. That is, they paid us to be a part of the sales package.
I am reminded of the old Joel on Software article "Things you should never do part 1": http://www.joelonsoftware.com/articles/fog0000000069.html

From the article:

"The idea that new code is better than old is patently absurd. Old code has been used. It has been tested. Lots of bugs have been found, and they've been fixed. There's nothing wrong with it. It doesn't acquire bugs just by sitting around on your hard drive."

EDIT: Joel isn't actually recommending "do nothing" - on the contrary - the article goes into some depth on ways one can improve software without throwing everything away and starting from scratch.
> For an information worker there are huge health downsides to being inside at home all day, even with a full family around.

This statement strikes me as odd. I can't really figure out what health downsides do you have in mind. Can you elaborate?

I would argue the opposite. Being an information worker in an office environment is deleterious to one's health. Humans are not designed to sit around in poorly ventilated rooms for a larger part of the day(light), where the only recourse from the unpleasantness of the situation is a fridge stocked with free sweetstuffs and soda. I've been there, eaten the Snickers, and am much happier now that I'm working from home, where I am able to take a short walk around the neighborhood, do a couple of yoga asanas or other exercise or even take a short nap almost anytime I want. There's also the fact that I can eat healthy food as per my liking, and not just one that is available in the cafeteria or nearby restaurants.

I am aware of the research and the reality of how important it is to not be alone all the time, but you really don't need the daily office-going grind to protect yourself from those particular dangers. In fact, at the end of my workday, I am eager to go out and socialize, whereas in my office-worker days, all I could think of was going home, cracking open a cold beer to decompress, and hoping that I don't have to talk to anyone for the rest of the day (not likely with family around).
What Happened with Ebola? (Opinion Piece)
Probably not what she meant, but Linux has a RNG that extracts randomness from CPU execution time jitter: https://lwn.net/Articles/642166/
You're going to have a harder time making this argument if the API is really completely internal. You could point out that it will be difficult to inter-operate with other programs or libraries though. I think your best bet is to show them that the spec already exists, there is already code that implements those specs, and they will have a lot less work to do (now and in the future) if they stick to the standard.
What's great about SockJS is it's meant as a WebSocket polyfill and nothing more. It also has some semblance of a protocol definition. This makes it an ideal foundation to build upon if what you really want is WebSockets, but you need a bandage for old browsers.

Meteor notably uses SockJS as part of their DDP spec.

Also Pushpin includes a SockJS to native WebSocket translator.
I'm down with "All (ok most) programming languages are simultaneously good and bad". I assumed it would go on to discuss Javascript, but nope. Which really goes to show how true the statement is.
"There is nothing to be gained." Not completely true, you could argue that it would be more maintainable in the future but I don't think that outweigh the risk of making changes here while it's still fully functional and nothing really needs it to change.
Sorry I wasn't clear in my comment, but at the end I state the same thing. The Schneier article is still true, but the linked microsoft research article needs an update.

>That all said the sentiment of the article still stands true. Users (like my family) hate worrying about security.

When I said "article" I was talking about the full document which gets directly into security best practice.

http://research.microsoft.com/en-us/um/people/cormac/papers/...

Also HN Comment guidlines indicate you shouldn't ask Did you read the article?

> Please don't insinuate that someone hasn't read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."
https://news.ycombinator.com/newsguidelines.html
How do you know it works? Did you test it on every platform?

What you would have to gain is maintainability. Maybe it's not worth it; maybe it is. But saying that there is nothing to be gained is just an opinion.
"history" == "past"

how can you ever move on if you keep dragging it up?

Hire the best. Simple. Efficient. Legal.

This company's operation is probably illegal (see parent post where i listed examples of how they discriminate)
No, I'm not on Vertex (Kalydeco), since I'm delta f508 homozygous, and that treatment was just approved.

Obviously I'm referring to retail cost. A quick peek at the most expensive ones, according to my insurance plan: Creon ($4500), Tobi ($7300), Pulmozyme ($5400), Cayston ($7200).
Personally I think PeerJS is a much more mature, robust and better documented solution.

http://peerjs.com/

Last time I checked PeerJS also provides support for handling TURN/ICE/STURN.
Chartio is hiring Senior Software Engineers to help bring BI to the masses
I've resolved this now, thanks :)
Mind pointing out which one? http://www.omniglot.com/language/phrases/yesnomaybe.htm
Once, but I hated it, back to the grunge and trenches for me.

Meetings every other day until 2pm? The same meeting 4 times with slightly different groups of people? Having to tell people they need to work overtime?

No thanks.
> So a more apt comparison would be a section that sells things that certain groups may find offensive - e.g., sex toys, confederate flags, bibles, guns[1]

Not a great analogy since the subreddits that are analogous to the examples you listed are all permitted on reddit without question. There are plenty of sex/flag/bible/gun related subs and nobody on either side of the reddit debate is trying to ban them. A better analogy would be if a group of patrons meeting up in one section of the store, proceeded to roam about the premises harassing overweight customers who are there to make purchases. Naturally, store management would seek to remove these individuals from the store so that the other customers can shop in peace.
That's not a slight nit-pick, that's me being an idiot. I'm going to delete my account and travel the world barefoot for two years as penance.
Open source Slack with Mobile app support
Choose your next programming laptop
Yep. There's nothing worse that maintaining code that doesn't change, or rarely changes. All that doing nothing because the code works, or works well enough, to avoid anybody noticing it. Yes, that's the classic example of why legacy code is a nightmare to maintain. When I think of maintenance, I think of constantly refactoring things that work.
I really wonder what advantage you think iran will bring to the US. Unless you think that radical islamism is a good ideology to spread around the world, and that the shariah may be a good basis for civil laws, because that's certainly where all the oil dollars earned by iran are going in the coming years ( just like saudi arabia spread its vision of islam in the past 30 years).
Again, there is no implicit accusation.
I am stating outright there was misbehavior. That is a statement.

What do you think the complaints to the SFLC and FSF from multiple parties were about ?

I don't see you complaining that neither of these parties gave details :)