skysight-inc/HackerNews huggingface dataset:
Not sure. One does not have a reasonable expectation of privacy in one's travels on a public street. Anyone (including police) can follow you, record where you go, photograph you, etc.

It may be true that, in the US, one cannot reasonably expect privacy in the various instants of their public existence, but when you aggregate those instants into a timeline then a reasonable person very much does have an expectation of privacy (otherwise stalking would be perfectly acceptable in society).

Outside the US, I would not be surprised if other cultures have developed a much higher expectation of privacy (or at least discretion and confidentiality) than the US.
Various Wikipedia's do have what you are imagining.[0] People are not normally automatically given the right to review changes and even if you do manage to review malicious edits they are easily reverted by others.

Every language has their own policies, but the English Wikipedia only has it enabled on certain pages.[1]

[0] http://meta.wikimedia.org/wiki/Flagged_Revisions

[1] http://en.wikipedia.org/wiki/Special:StablePages
> disqualifying half of the candidates for cheating was tiring.

That actually sounds awesome. You could reduce your interview evaluation overhead by nearly 50%!
Ok. I haven't started going into the specifics about the protocol implementation but its about encrypting the message end-to-end. It still does not solve the problem of ownership, privacy and ads.

Having said that, If implemented we would definitely take advantage of the protocol.
Some thoughts about dailys as we've started to embrace some scrum elements over the last few years.

I've found they are more valuable on some projects than others because of the number of people on the project, how sharp they are, timeline and amt of work to be done, etc.. We've found them more necessary in projects with larger groups and shorter timeframe.

One counter-intuitive thing about them. "Oh great another meeting".. You may get back some time spent on email correspondence or impromptu meetings when every issue has to be emails back and forth. Just hold it until the next standup.

The author said you don't want to wait 8 hrs until the next mtg to alert the PM of a blocker, but often you can make progress on other tasks - save the emails - or even worse - the impromptu meeting. Often, it can wait until tomorrow.

Most important, don't let the standups get off track. Either a PM who tries to turn it into a regular meeting. It's not a 30 or 60 min. status update they may be used to. Or - who lets people run wild. It's 15 minutes and that's it - and take things offline.
Unless the only hospital nearby is a Catholic-affiliated hospital. Or you live in one of several states with little to no access to abortion providers.
The transport makes a big difference. Is it going to stop working as soon as I cross the Canadian border? Is there a per-message fee if I am communicating with someone in another country? Is it going to stop working if my phone is connected to wifi and the router is broken or misconfigured, like it is at the coffee shop down the block from my house?

It's one thing to send an email, another thing to send a text, and another thing to use some proprietary messaging protocol, even if all three can be initiated by poking at the same device in slightly different ways, and I want to know which one I'm using so I can pick the right one for the situation.
Indian police to use pepper-spraying drones on unruly protesters
Which violates one of the main principles of Agile - "Responding to change over following a plan". That's worth bringing up in a sprint review.
perfect! that's all I wanted it to do anyway.
Who makes that argument? Daylight savings doesn't give you consistent sunrise/sunsets.

For example, in Melbourne, Australia, in the winter it will be dark by around 5:30pm. In the summer it gets dark by around 8:30pm. I like having inconsistent sunrise and sunset times (e.g. extra daylight time in the evenings in the summer).

Neither do I think daylight savings extends the amount of daylight. What it does is shift the typical working day so that by the end of it, there are still a few more hours of daylight left. That's what I like about.
An interesting article. Given I'm also raising a family with a spouse with very different religious views, I understand her feeling of "...but I thought she would pick my way!"; no doubt I'll be feeling a lot of that as our children grow up. But I think some of her doubts about her own childhood are misplaced: she grew up in a very open culture, and so knows of the positives of it, and the negatives. And while she's seeing some of the positives of her daughter's choices, she's as yet unfamiliar with those costs. So it's easy to think "maybe they're not there, maybe this can be a better way to live." But the costs are there, she just isn't as intimately familiar with them yet.
Phone Surveillance Revelation Should Prompt Reassessment of NSA Spying
Thank you for this comment.

Adding anecdotal evidence using a throwaway for obvious reasons (some minor details changed for the same):

A long time ago in a location far, far away, I was hired into a mid-size (300 employees), relatively successful, few-years-old B2B startup (growing, starting to become profitable) to sort out major issues with a department that happened to be my specialty.

I rapidly figured out the problems stemmed from the top: the head of the department was a woman with an MBA who was utterly incompetent at her job, and who had been there for about a year and a half to build it. I came to this conclusion in various ways.

First, her work was abysmal when I looked at it, and demonstrated complete ignorance of the technical field she was supposed to work in - she had an MBA and her attitude was "I don't need to learn anything technical because it's my underlings' job", but her underlings had about the same technical skills. Her lack of output adversely impacted fundraising for the C round, which strained the company finances and caused management to hire me in desperation.

Second, every single stakeholder I talked to in the company - from heads of departments to junior staff - thought she was abysmally incompetent and her work was severely lacking. In some cases, the frustration was so strong as to border on the personal. I talked to over 40 people and could not find a single champion of her work. It was clear that the company expected me not just to fix her problems but to make a good case to get rid of her as well.

A month into the project, I realized management was very evasive whenever I tried to bring evidence to the case to be made to replace her. I learnt through the grapevine that she had gotten the management team into a room and announced her pregnancy ("hey guys, I have some really good personal news to share with you!" - yes, she was that transparent). The news spread gradually throughout the company, and as it did, an eerie silence replaced the comments as stakeholders resigned themselves to their fate.

I left the project unable to effect the change I had been hired to do (she refused to use any of my work and blocked anybody else from using it), and she was still employed there two years later.

For what it's worth, I've seen plenty more evidence of bias in the other direction, including an employee I had personally hired for her exceptional skill who was later fired - I am about 80% certain - because my replacement as team lead didn't like working with women (he argued budget cuts but she was the only one fired in a team of 30). But thought I'd throw this story in as an example from the other side.
Yep, I think that's a big problem. It shouldn't matter if you're still at the company when the redistribution happens, it should just be based on how many shares you own.
I tend to have a problem with managers who think doing Agile™ yields a better quality product.

I've done agile agile (the process being agile) before which worked great. 3 week planning with one to three tasks per week and weekly sync, no detailed estimates. This was pleasant, I felt trusted, empowered and as a result more committed.

Right now I'm doing the full cargo cult Agile, with daily standup, sprint planning, backlog grooming, sprint retrospectives, end of sprint demos. I get regularly dinged for not following the process, never mind if the work is actually done. Also there is 5 manager/pm at our standup, for 6 engineers.
I don't know for you but this kind of stuff makes me completely indolent, before I start searching for something new.
Revoking an OCSP Responder
La série House of Cards reconduite pour une saison 4
Polygyny in Islam
1 year ago: https://news.ycombinator.com/item?id=8176458

2 years ago: https://news.ycombinator.com/item?id=6296201

3 years ago: https://news.ycombinator.com/item?id=3802458

4 years ago: https://news.ycombinator.com/item?id=3114391

5 years ago: https://news.ycombinator.com/item?id=1293652

6 years ago: https://news.ycombinator.com/item?id=385068

7 years ago: https://news.ycombinator.com/item?id=123489
Stop beating yourself up and start working as you have wished. Work when it is time to work but don't forget to live. You will never get that time back but are still young.

Don't be afraid to fail. Push ahead and you'll see failure is temporary.
VCs Are (What Google Thinks)
This one comes up ever 3-4 years or so in sysadmin communities, and I read it every single time. because it's worth it.

It's one of those things that I highly doubt would have occurred to me to have even checked, or given even a moments thought to, under normal circumstances.
Maybe the submitter is one of the ten thousand https://xkcd.com/1053/

Bet there are a few more that will find this submission too.
Last time I went out interviewing, I whipped up a fun little Android game, put it on my phone, and made a point of finding a way to slip it into the conversation. It was great because:

1) It let me set the tone and path for much of the interview, since so many places do unstructured interviews.
2) It was a concrete demonstration of my skills.
3) Java and mobile are both hot technologies, and the game also made effective use of other common stuff like Open GL, multithreading, network, database storage (via sqlite), etc.
4) Spending a few minutes playing a game sets a relaxed tone for the entire interview, which makes things easier for everyone involved.

Structured interviews really are a brilliant strategy. Whenever I interview, I do my best to subtly direct the interview in a way that exposes my strengths and leads the conversation into areas that I am most comfortable with (and trust me, whipping out a concrete example full of technologies that you're absolutely comfortable with helps). A structured interview, to an extent, would allow the employer to retain better control of the interview (whether or not the realize it), which is probably to their benefit. For instance, I teach Java, C#/VB, and some other modern languages at a local college after work, do tons of C / embedded / network / etc. stuff at work, and do digital electronics for hobby ... so if you let me push the interview in those technical directions, I'm at an advantage.
Has anyone had their pull request for a bitcoin miner accepted yet?
...come into work earlier, leave work earlier. It's just an hour.
That's not the nature of activism, friend. If you're spending most of your time talking to people who don't or won't listen, it's because you aren't communicating effectively. People listen when you communicate effectively.

That said, do not ever confuse people listening for people agreeing. They are very different things. Just because someone honestly listens to you does not mean they will come to agree with you.

Also, people listen when you are willing to listen to them. Too many "conversations" are thinly veiled preaching.
Come on, everyone knows that unit tests run counterclockwise in Australia. How could you expect it to succeed?
>which is to motivate me to do something today which I will be able to talk about tomorrow.

If you're not motivated to do the items in your Sprint anyway, then you got a bigger problem than what your standup can fix...
It looks like the average employee at Facebook would have received $4.5 million.

Once the IPO happens and you pay your employees $4.5 million, their $100-$200k salary doesn't seem worth much anymore. What actually would have happened to Facebook, if they did this? Is it possible that the company collapses, while too many employees quit so they can do their own thing, or retire? Would they have had to double or triple everyone's salaries to keep them on board?

I could see it being a disaster. It could also significantly de-value a company's IPO (or sale) because the investors would see this as a massive risk. At least until it's been tested with a company that IPOs.
jailbreak iOS 8.2 use free TaiG 1.3 and iOS 8.3 jailbreak
Exposing the Murky World of Online Ads Aimed at Kids
> Abortion is, fortunately, always a choice in the US.

Legally, it is sometimes a choice in America (many states have restrictions, both within the bounds which have previously been found constitutional by the federal courts and in many cases outside them and likely to be challenged in the future, but enforced until such a challenge happens and succeeds -- and there is no guarantee that a challenge will succeed, even if the precedent suggests it should.) Practically, it is even less of a choice than it is legally, due to various factors, including the restrictions, driving abortion providers out of large swaths of the country.

http://www.thedailybeast.com/articles/2013/01/22/the-geograp...

http://www.huffingtonpost.com/2014/10/08/texas-abortion-acce...

http://fivethirtyeight.com/datalab/maps-of-access-to-abortio...
Coding and associated work efforts are largely individual. You sit (or stand) at your computer and work alone. But in reality you are working in a group. The standup reinforces the team nature of the overall effort. Humans are naturally social, but the computer engineering work effort is done largely individually. Something is necessary to maintain the social element and that's where standups come in. Other meeting patterns could work, but one at the beginning of the work day where everyone "checks in" seems to work well from the standpoint of managers whose job it is to corral independent workers of different strengths. If your team doesn't need a standup that's great, but if the team starts to need one you will wish you had been doing it all along before the balance got out of whack.
Consider it the price you pay for potentially spending the balance of your day unmolested.

When I ran agile-driven development teams it really helped me and my team in three ways: 1) any blockers they needed to escalate got to me at 9 AM not at 11 or 1 or whenever is more convenient for you, op, 2) it made it immediately clear who was not making progress, 3) it kept people honest about staying focused solely on their story.

The latter was the most valuable because I had people who would agree to let (for instance) our deployment tool handle differences between releases as it was designed by the vendor, and then try to check in a zip or tar file because they couldn't be sure about the deployer.

Or my guy who would agree to bang out a simple static page and next thing you know he's trying to write a framework. Some of these people were new to agile but the process including the standup helped me break them of a lot of bad habits.

Still, I feel ya about early meetings. My boss is in a later timezone so my day starts at 7 local time, man. It could always be worse.
Seems like a lot of the girl's peers are Muslim. The people she interacts with and values and respects (which includes her peers to increasing degree as she gets older) will have a significant influence on the way she dresses I imagine:

> In the following days, Aliya wore her headscarf[] to a Muslim gathering where she was showered with compliments

I'd predict a social interaction like that - wearing headscarf means acceptance and praise from peers - to hold more sway than feedback from mom, past a certain age. Parents do not have complete insight into the difficulty their children have fitting in, nor how much thought or care they spend toward that purpose. What child wouldn't don an article of clothing that makes them instantly more accepted?
I would like to proffer a different strategy: Pick something that you are passionate about, good at, and comfortable with. Then push your personal boundaries and learn something new while making some app/widget/whatever, even if it's been solved/done before. Why did you do it? You wanted to stay up to date, learn something, and it was fun (and all of this will be true).

Whatever you made will probably be something pretty sweet because you chose something close to your heart, not something that was simply 'unsolved' or 'needed doing'.

Employers will love that you chose to challenge yourself to build new skills as a hobby, and because you chose something that you are passionate about, you'll probably also have a good amount of enthusiasm while you talk about it, which is equally important.
I've used Slate for 2 years. Slate hasn't had an update in 2 years. It was supposed to be replaced by Zephyros, no Phoenix, no Hydra, no Mjolnir, no ...

Despite the lack of updates, Slate is what I still use to this day. It still works, and it does the job well.
That's all well and good, however I don't think it comes close to justifying the complexity.
> Unless the only hospital nearby is a Catholic-affiliated hospital.

Elective abortions generally aren't mostly performed in hospitals anyway, but in separate clinics, so what kind of hospital is nearby is largely irrelevant (it might have an indirect relationship in states that have adopted rules requiring abortion providers to be doctors with admitting privilegs in a nearby hospital, but those rules have, IIRC, only been proposed in places where none of the elective abortion providers meet that description in the first place, and are intended as a backdoor prohibition on abortion.)
We can't have either.
If an early employee leaves, they don't get to participate in the kicker pool. Suppose it takes a company 10 years to have a significant liquidity event. In the timespan, it's very likely key employees join & leave and don't best a stake that would achieve financial independence. Shouldn't these employees also have access to the kicker pool? A relevant example here is Quora, where several very key engineers have left but (I'm assuming) wouldn't achieve financial independence in an IPO. Isn't this system a bit predicated on a high growth company that hopes to IPO within a few years? What might help is giving option/shareholders access to the kicker pool so long as they don't liquidate otherwise.
>Swarm

http://www.gocatch.com/

Pretty neat idea, although GoCatch isn't very big here in Brisbane!
I received a threat after I revealed the city and company, so probably not something I can substantiate without risk.
I see this story every so often, and it's good one, but haven't thought to verify it. Has anyone else?
Kununurra have the opposite problem - they are on AWST but are only about 400 kms from Darwin. So the sun comes up at 4am and sets at 4pm.
The GPL applies to "derivative works", which is a legal term without a precise technical definition.

If you decide to write an interpreter for an existing language, and run existing programs on it, then those existing programs "probably" do not have to be under the GPL, for definitions of "probably" that Legal will not be happy about.

If you write an interpreter for a made-up language and then write programs in that language as part of a thinly-veiled scheme to do an end-run around the GPL, then that "probably" violates the GPL.

There is currently no bright-line rule separating those cases; this is something IP lawyers argue about themselves and reach wildly different conclusions.
lsof -c <command name> eg: httpd
One of the most important things that I've learned over the years is that the Daily Stand-Up is a tool that solves a particular problem.

Specifically, if you have a team that doesn't communicate effectively on a daily basis, then the standup gives you -- the manager -- a place where you can get and keep your developers on the same page.

When everybody already knows what's going on, then the standup loses a lot of its meaning, and should get cut down to "Anybody blocked, or need anything they don't have? Everybody good to go today? Okay, let's make this happen."

But at a lot of companies, it goes the other way, turning into a Kafkaesque version of Show and Tell.

Most people that end up in technical management don't get any serious coaching on leadership or management. This leads to a lot of management-by-bestseller, cargo-cult agile, and the sort of dystopian teams that grind the minds of otherwise talented developers into useless pulp.

It's not that these managers are incompetent or bad-intentioned, just that they never got any solid guidance on how to lead, manage, and grow a team.

What's truly insidious is that the problems don't really start becoming catastrophic for months or years, by which time it's very, very difficult to turn the ship around.

One of the more powerful tools for fighting this sort of problem is the retrospective -- a weekly block of time where the team goes over what works and what doesn't -- but, more often than not, the retro is the first thing that gets cut from the process because "nobody has time."
Where did the term "offline" come from? It's bewildered me for the past decade. It's always used in a meeting, which is inherently "offline".

It's also always code for "this is going to get ugly", or "this actually involves thought". So again, don't really get why "offline".

Additionally, I find it amusing (and agree with the author about standups btw) that anything which actually requires discussion among team members, and is interesting, and usually...worthy of us MEETING with each other...gets ordered out of the "meeting". Mundane status updates generally get ignored while everyone else looks at their phone or fidgets.
Now it is starting to look like the contents of a typical hackathon submission.
Loudly sneezing, blurring your vision, and ruining your sense of smell are really not conducive to surviving an encounter with a big cat.

I mean, you might piss it off if you sneeze on it, I guess. Yay?
I triple checked before posting this, looks like someone edited the blog ;)
Ahead of its time: The history of Looking Glass
Thanks. Let us know if you need some particular additional feature.
Once again - I continue to get more value out of this HN thread than I ever did in high-school physics. You are distinguishing between a "real force" in terms of something that can be objectively measured irrespective of things like inertia, versus "real force" as measured as a function of the basic four-forces. What I think your saying, is just because a force "appears" in the equations in a rotating frame of reference, doesn't make it real.

Curious - which of the four forces are the source of the centripetal acceleration in a tilt-a-whirl?
Once a year is about the right frequency. Recurring stories is one way in which a community shares and perpetuates its culture with newcomers. Some of them are a delight to read on that yearly cadence, like the SR-71 story about a pilot and his copilot becoming a crew.

That said, it's wise to consider the frequency with which such things appear, individually and in total. Too much repetition and focus on memes becomes dysfunctionally self-obsessive. Not sure what the right answer is, but I can probably deal with once per year, short time on front page, and small % of total content.
- Four spaces at the start of a line makes 'preformat',
useful for code or lists.
- You'll want to manually wrap long lines, though.
A mysterious connection between number theory, algebra and string theory?
Ha, I'm one of the ten thousand for both the XKCD and this post. Lucky me!
Show HN: University Crime Watch