skysight-inc/HackerNews huggingface dataset:
Well, there are more details to the story that the author omitted. Here's a few from a comment on the article:

The article appears to somehow have missed some key pieces of information. I leave it to you to decide whether Mr Klug and Ms Sudarshana Bannerjee's motives are:

1) Brian Klug, a disgruntled previous member who was banned from the premises failed to submit tax returns on time when he was executive director of the organization

2) Sudarshana and Mr Klug were romantically involved in the past

3) Sudarshana applied for the Executive director position at the organization in late 2015, with a salary of around $55,000, but another candidate was selected.

4) During the time of her election and investigation, she was unemployed.

5) She has previously admitted being friends with Marie Knox (who in turn, was hired by her former boyfriend, Brian Klug)

6) Sudarshana resigned just before a board meeting where a conflict of interest vote was on the agenda, stating that no current or former board member would be eligible for a paid staff position (all board members are unpaid volunteers)

7) Sudarshana resigned as soon as she received confirmation of a new paid position, apparently working with the Kamala Harris Senate campaign.

Sudarshana was not forced out of the board, she resigned herself. She posted her resignation on the HD slack channel.

Mr Klug is also the person who created this submission (dustball)
To clarify, pull requests shouldn't be squashed before review. They should be squashed when they get merged in, like this GitHub feature does. The granular commit history is useful during code review. It is not useful as a future developer trying to evaluate how the behavior of the program changed over time.
I think it's clear he understands how it works.

> what you are saying goes against Tor's principals

That's why it will probably never be cleaned up. That's also why more and more people will probably block access from Tor. CloudFlare says they get a 95% attack rate from it. A blog post the other day said FotoForensics gets about 91% attacks from Tor.

No one is going to put up with 91% attacks for long. And if that means Tor becomes it's own walled garden that doesn't 'interact' with the public internet, so be it.
HipChat was acquired by Atlassian, so they didn't make it. :)

I don't find our self-hosted Jira slow or a throwback to the 90s. It also cost $10. But these things are opinions. :)
Ask HN: How do you diversify your income?
As I get older, I'm trying to focus less on absolute financial independence than a sort of income redundancy, where I have enough sources of revenue to sustain my barest expenses in case something goes wrong.

My dream: four or five streams, requiring different levels of investment and labor, but generally clocking in under 40 hours and, to the point where I could lose one or face a serious cutback in two, and never be in jeopardy.

I know this overlaps with the passive income obsession, so I'm excited to hear HN's thoughts, but I'm concerned less with overall effort than reducing the risk tied to my income coming solely from my job.

I'm super interested to hear if any HN'ers have tried to diversify their income outside of tech, maybe through some small-ball physical investments like ATMs or vending machines?

background: late 20s, FE dev, small amount of savings, no debt
> and can't be dependent on a prior PR.

This pinpoints the major problem exactly. Without dependencies between PRs there's really no sane way (with this feature enabled) to submit a series of commits while expecting those commits to remain separate.

Oh, and I object to the general sentiment in the responses to your post that seem to value drive-by/inexperienced contributors over the "experts". Yes, we definitely should make things as easy/simple as possible for new contributors, but NOT at the expense of adding a gotcha for expert contributors. The experts are what keep a project going over many years instead of just releasing version upon version of trivial spelling fixes.

(And, btw, the default "merge" option for GitHub PRs also sucks. It should be possible to simply disallow non-FF merges and to force all merges to be FF. EDIT: Interestingly, this seems to be about the only workflow explicitly forbidden by the new rules... unless, of course, you're willing to merge everything manually using your local copy of the repo and pushing from that to GH.)
That red is the safest light.
I'm no JS expert[1] but this doesn't look correct:

# https://github.com/marlabrizel/genius-blocker/blob/master/lib/genius/blocker.rb#L11
var annotated = window.location.href.indexOf("genius.it/") != -1;
if (annotated) {
window.location.href = window.location.href.replace("genius.it/", "")
}

Wouldn't this match any instance of "genius.it" throughout the URL, not just at the beginning?

For example it'd match "https://example.com/blog/how-to-block-genius.it" and redirect the user to a (probably) non-existent link with that string removed.

[1]: I just play one on HN.
The problem is that Slack is not the only tool jockeying for a few dollars per employee per month. Hipchat, while not the cool thing anymore, is also much cheaper.
https://genius.it/8917326/news.ycombinator.com/item?id=11406...
> Oops! Something has gone horribly wrong!

Not terribly helpful.
TL;DR: The relatively small group of people who learn how to code will have good jobs writing automation software that will cause the unemployment and misery of the larger group who don't know how to code. There won't be enough good coding jobs for everybody to have one, though, and they won't last forever as competition for them is bound to increase, so it would be better if you stayed in the latter group.
Wow, there was essentially no information in that blogpost. Here are the relevant sentences:

> My understanding is that after the Macintosh-crazed 80s, he ran into some issues. Suffice it to say that I see him on the street at least a couple of times a month.

Might as well have said nothing at all.
I suspect that the similarities between the S and the 3 are partly due to the aerodynamics of the S translating into the newest member of the family. Why throw out all of that testing and a widely recognized signature look?

I really doubt that the 3 will feel nearly as posh inside as the luxury S. The status is in the level of interior design and premium interior materials.

Nor will the 3 be quite as smooth to drive, have the battery life, or the powerful motors that the S has.

Any auto maker could do the same thing. A Corvette with basic interior and a midline motor would not cost any more to make than an Impala.

In fact, I think that the 3 will decrease the manufacturing costs of the S because of the economies of scale in producing the shared parts. There will be many, many more 3's on the road than S's.

I just hope that Tesla eventually makes its own coupe/sports car with the same common and luxury models strategy. I don't need a 5 seater, because I don't have kids. I also don't need an $100k-$150k coupe. $40k-$45k would be a great price point for the non-luxury package to undercut the other auto manufacturers' entry level sports cars.
HEAT Software | Scottsdale, AZ and others | Full Time - Onsite

HEAT Software is leading the unification of Cloud Service Management and Unified Endpoint Management (UEM). We empower IT, HR, Facilities, Customer Service and other enterprise functions to simplify and automate their business processes to improve service quality, while managing and securing endpoints to proactively detect and protect against threats to business continuity.

Specifically I work within the endpoint protection groups and the positions below are ones that I'm personally familiar with and on the team.
Open Positions in Scottsdale:
- Senior Software Engineer (8+ years): http://app.jobvite.com/m?3I6oUhwS
- Software Engineer II (4+ years): http://app.jobvite.com/m?3JcoUhwZ

Both positions will be working within our group that develops our SCCM plugin (Microsoft System Center), and working on automation that helps expand our HEATSoftware patch content used in SCCM and our partners. Good working knowledge how operating system update processes work for Windows or Linux is a benefit, but not required. Ability to work against 3rd party web services to mine data is a plus as well. More detail is in the job descriptions themselves.

Technical Skills Needed:
.NET, C#, JavaScript, ASP.NET, C++, SQL Server, MS IIS, CSS2/CSS3 and HTML/HTML5
Experience with any of the following Unix/Linux/MacOS, in a development or personal capacity.

Feel free to apply using the links above for the teams I work within, or look at the other listings directly at http://app.jobvite.com/m?3wboUhwL for Milpitas, CA | Colorado Springs, CO | Filderstadt, Germany | Galway, Ireland
The Muse | NYC | Fullstack, Backend (onsite or remote) | Frontend, BI (onsite only)

At The Muse, we offer advice, coaching, and a job experience that's actually engaging and doesn't suck; we reach millions of users every month with an engineering approach that is grounded in data analysis and best practices.

We're looking for engineers across our entire stack—backend, full stack, and frontend. For more info, drop me an e-mail at marco@themuse.com, or apply here:

https://www.themuse.com/jobs?company=The%20Muse&filter=true&...

We use a microservice infrastructure based on Python 3 and Tornado, Mithril, and CoffeeScript. We are happy to consider engineers with experience in Rails, Java, and Go, as well as devops and data science specialists.

Our engineering team is growing all the time, with plenty of opportunities for leadership and mentorship roles, or to pick up new skills if that interests you. We frequently contribute to open-source, give our engineers a great deal of agency in picking the problems they want to work on, and have a strict no-asshole policy.
Universities are not what they used to be. They are not bastions of free speech and thought. They are not a place to challenge ideas.

They're an extension of high school. Their environment is an extension of the environment of corporate America. Going to university is a business transaction - time and money go in, credentials come out.

People go to universities to get a piece of paper saying they are capable of passing a series of classes. They rarely go to feel challenged, and often don't even go to learn. They just need to prove, without expense to future employers, a basic level of competency in following instructions.
Considering they're (supposedly) profitable, have hundreds of employees, and it doesn't cost $200m to do this -- doubtful.

It's highly unlikely we'll ever see an on-prem Slack.
After completing a feature (or part of one) I often "squash" manually by performing a mixed reset from the tip of the in-development branch back to a good parent commit.

This leaves all of the feature's changes in your working copy, which you can then stage by line/hunk and individually commit in clean, atomic pieces with the benefit of already having written the final code.

This removes the in-progress commits like a Squash, but pieces of code can still be brought in as individual easy-to-review commits. And it's potentially easier to understand / perform manually than rewriting history via a git command that would do the same thing.
Postmates Plus Unlimited: free delivery on orders over $30
I don't mind being stuck with WebKit, but what I do mind is being hold back by limiting browser features and not implementing APIs that other engines already provide for a long time. Currently our biggest issue is not being allowed to play videos inline on a page. But the missing Fullscreen API also costs us additional development time.
Take it a step further and you could say "since date 20xx-xx-xx until now" for each user and really piss off a judge with your cleverness. After all, youre not saying when a user's info was subpoenaed, but the range of dates when it wasnt.
As a person that sends dozens, sometimes hundreds of emails a day, I click the button that's I always click.

A UI that requires the user to read every button and look at every icon that they click on because it may have been changed to do something completely different is a terrible UI.

While I might notice a new color, I'm not certain that I would.
Data Architect, New York NY, full-time, ONSITE

Ad tech company hiring data architects and developers with Java, Kafka, Storm, and big data experience. PostgreSQL and Python a plus. Three or more years of experience, please.

Contact patrick (dot) may (at) ignitionone (dot) com with your resume and links to your GitHub repos and/or blog.
Do you see the rubber pads on the floor and the dirty chair in front of the operators console?

Surely it cuts down on the number of operators required compared to mid-20th century production methods, but these machines still require dedicated people to set the up and supervise.

One positive difference is that an experience machine operator may now have a career path open didn't exist in years past: he could move up to the role of a CNC machining programmer.
Vim in a current terminal does indeed support entering unicode. I can even type it by value, see :help utf-8-typing
Right, sometimes. Pull requests are not necessarily a "unit of change" like you mentioned, though. For example, the first link I gave should not be squashed. But I don't want it to create a merge commit either.

I'm a little underwhelmed with the feature, it looks like it's either "squash everything" or "make a merge commit". There's no option to rebase & merge and/or selectively squash.
Curalate | SEATTLE | NYC | PHILLY
www.curalate.com
(roles can sit in any of our offices)
Curalate is the leading visual commerce platform, connecting pictures, people and products. We sit at the intersection of big data and computer vision and we help brands create authentic connections with consumers through images!

* TechCrunch: Curalate Raises $27.5M to Help Brands Connect Content to Commerce
* One of the nation’s 25 Hottest “under-the-radar startups” by Business Insider
* Inc. Magazine: The 10 Hottest Startups to Work for in NYC (Curalate is #1!)

ALL ROLES CAN BE FOUND HERE: http://grnh.se/6k3bhl - Full Stack Engineer - Front-end Engineer - DevOps Engineer - Product Manager - Product/UX Designer

We hire developers, designers and product people with exceptional problem solving skills, creative out-of-the-box thinking, and comfort with quickly learning, evaluating, and deploying new technologies. Also, We're not language zealots; we believe in using the right tool for the job, and are comfortable with a polyglot codebase.
Hah, that's actually pretty funny.
Yes the Readme (if you follow the link) states almost immediately that you need an API token and session ID, etc..
Someday when you accidentally click the wrong button in something, perhaps when you are old or suffer from some disability, I hope that you remember this comment of yours.

Furthermore, the icon doesn't have anything for you to read, since it uses an image (whose meaning may still not be clear to an older or disabled person; it kind of looks like an ice cream cone to me).
I hate squashing branches. There's a lot of value in commit messages; they're educational and are a form of documentation. It's on the developer to squash the "oops" commits, during a rebase, rewriting the commit message so it has some value when going back in time to look at changes.

I'd love to see a commit linter, that points at commits with text like "oops" and "fix my derp" to suggest possible commits to squash.

Git history shouldn't resemble a hot mess, but the evolution of code should be pretty granular. I'd take the hot mess over full squashing, though.
Oh god, this is triggering my PTSD already! On the other hand, a language-enforced style guide might not be such a bad idea...
Is this a wording issue?

> Akamai found that the "conversion rate" of Tor IP addresses clicking on ads and performing commercial activity was "virtually equal" to that of non-Tor IP addresses

So when seeing actual web traffic things are identical. That only measures real web traffic. It doesn't measure all the SSH attacks, SPAM being sent, possibly checking for vulnerabilities and unpatched software/etc.
Does it work if you reply to yourself?

Edit: it will not allow you to delete a comment with any replies, even your own, but if you delete your reply, you can delete its parent.
One area they could improve (besides the obvious one being video chat) is integration with other bug trackers. The Jira plugin is quite pathetic. Granted, Atlassian owns hipchat AND jira, but hipchat's jira integration is excellent. The slack plugin for jira is pretty terrible and is why $employer went with hipchat sadly.
$ git checkout master
$ git pull
$ git checkout branch-name
$ git rebase master

If there are merge conflicts, open the affected file(s) and resolve them. Then:

$ git add filename.ext
$ git rebase --continue

Finally:

$ git push origin branch-name

If you've already pushed the branch, use -f. Make sure to always specify the branch name when using that flag!
It's not really all that interesting, is it? It's what every business does; to try and make money from you. They make films you want to watch, books you want to read, music you want to listen to, and websites you want to read. Even blogs.
The further we get into the future, the more it resembles Snow Crash to me
> Same reason we don't allow the vast majority of customers to entirely block traffic from an entire a country, even though it's one of our top customer support requests.

https://www.cloudflare.com/features-security/

> In addition to CloudFlare’s automatic detection, you can easily add an IP address, IP ranges or entire countries to your Trust and Block list.

Umm, vast majority is non-paying I take it since I believe its available on every paid plain?

https://support.cloudflare.com/hc/en-us/articles/200170056-W...

> A low security setting will challenge only the most threatening visitors. A high security setting will challenge all visitors that have exhibited threatening behavior within the last 14 days.

I'm guessing you mean the "Essentially Off" option which implies Cloudflare basically stops providing security?
iCloud Down
iCloud went down, with all calendars going down, people unable to access mail via the browser, and iCloud storage in iPhones showing an error. 100s and 100s of people on Twitter contacting Twitter about the outage, but surprisingly to each person they are acting as if they are unaware of the issue and still haven't updated their status page in regards to the outage. Some services such as calendar are coming back online, but very odd Apple is not updating the status online or letting people on Twitter know it's happening to everyone.
They probably don't want hostile/parasitic services profiting off their content for free, even though that seems to be the business plan of every other startup. If Genius wants to act in good faith they should let people opt-out of annotations on their sites / pages.

Also, it's just another walled garden for content from a company with past ethically questionable business practices.
Google designers ARE intensely incompetent. And design's a pretty simple subject area. The problem is, designers need to justify their continued jobs, after a product is launched. So there's a constant set of increasingly more complicated overengineering projects to "redesign" things to stay "trendy". Generally sacrificing usability in exchange.

Ever since Google hired their "VP of Design", their products have heavily shifted away from being functionally useful.

There's a reason Gmail is the last bastion of competent design at Google. There's a reason that even Googlers said they wouldn't use Gmail if Inbox became the "new Gmail", and this is probably where this conversation rounds back to this prank:

You don't %$@# with email.
Generating Large Images from Latent Vectors
Ah, but not everyone eats fast food, so there must be a way to resist them.
I'm honestly astounded that so many high profile corporations are willing to use slack without an on-premise version.

Slack is the only SaaS that has access to, and STORES PERMANENTLY, every important private message, group message, document, commit, internal URLs, .... of your company.

At some point in the future, slack will get hacked. Every sufficiently popular product does. It's only a matter of time. And when it does, the data hosted by slack will be an absolute treasure trove for competitive intelligence, "insider" trading, hacking, and a variety of other bad, bad things.

Not to mention, an arbitrary number of employees at slack can read the internal communications of any company using their product. I'm sure slack has some "security" measures in place to prevent this, but it would only take one rogue employee with the keys to the kingdom to snoop on any data imaginable.
This seems incredibly dangerous to me...
Or if the proxy shows up in search results higher than the original site.
Sometimes I feel like it's a minority position, but I think it strange all the efforts people go to in order to essentially make the git DAG look like a (lie of a) straight-line CVS or SVN commit list. Seeing how the sausage was actually made (no rebases, no squashes, sometimes not even fast-forwards) isn't pretty, but it is meaningful and will tell you a great deal about a project and its developers... I trust that. It's real and visceral and how software is actually made and you can learn from that or find things to explore in that jungle. Projects with multiple developers that yet have straight line commit histories and super tidy commits are aberrations and full of little lies...

Kudos to GitHub for providing this feature that a lot of people have asked for. I obviously don't plan to use it, but I appreciate that it's an option for those people that like their small, harmless lies. ;)
I have a feeling that the perceived lack of "product" side projects corellates to the rise of Github and "open-source contributions" as a requirement to get a tech interview?
People spend all their hobby energy trying to build github portfolios that most of the time is just libraries or contributions to libraries.
Ten of the most commonly confused words in the English language
This, as rebase, is a great idea for people who would rather use SVN instead, but have to use git for some reason or another.

I mean, if you want your history simplified into a linear squashed series of commits, why the hell do you use VCS which models a history as acyclic directional graph in the first place?
I also really wish that they would revert this change. But maybe Google+ was created just because they wanted to get rid of the + operator in Google search?
There's no guarantee, but there are many benefits to striving for this ("git bisect run", CI test results).
Search indexing is disabled.

http://genius.it/robots.txt
Drop mic wasn't bad. People are just stupid. And you're a sheep for just going along with the "it's the worst prank" train. Start thinking for yourself Joshie.
I wish the part about renaming PyPI back to Cheeseshop were true.
A few tips!

1. Always use the "upstream" branch as your rebase target - "git rebase -i master", or " git rebase -i origin/master". This is almost always what you want, and picking the wrong base is the most common error I've seen when teaching people rebase -i

2. Use autosquash! https://robots.thoughtbot.com/autosquashing-git-commits. If you have trouble with the text-editor interface you get when you run rebase -i, this will both handle its usage, and in the long run give you some visual examples of how the interface is supposed to be used. If you're really into this, set the config option "rebase.autoSquash true" to avoid the extra command-line flag.

3. If you mess up and realize in the middle, git rebase --abort.

4. Use the reflog after the fact for both finding and undoing mistakes: git diff branchname branchname@{1} to check for unintended code differences, and git reset --hard branchname@{1} to undo the rebase.
Omnichannel Retail and the Changing Costs of Fulfillment
Separate, support, serve [Was: Embrace, Extend, Extinguish]