News for hackers. Stuff that matters.

brennenHN

I think you should re-read what you quoted. He said "Berlin is in fact NOT the only timezone which had a 2 hour DST"
Re:Stop Freelancing on Wednesday November 13, 2013 @02:44PM (#6727892)
This is the kind of positive practical advice I wish there was more of on Hacker News.
Re:Why the iPhone 5c is Brilliant on Thursday October 17, 2013 @02:55PM (#6567407)
I have some theories, but I think there are a lot of different agendas at Google that make it hard to parse the strategies behind a product release.
Re:A 3D printed toothbrush for all your teeth on Tuesday October 01, 2013 @03:20PM (#6478465)
One weird trick for whiter teeth!!!
Re:Why I Moved My Startup to Oakland on Tuesday September 24, 2013 @08:09PM (#6441769)
Awesome! Definitely will do.
Re:Why I Moved My Startup to Oakland on Tuesday September 24, 2013 @07:40PM (#6441616)
This is a good question, and I have two answers. 1) You are paying a high premium in San Francisco for the privilege of that stuff and it's simply not worth it. 2) The culture is pretty affected by the echoing and it gets kind of hard to escape. For example, going out to bars people frequently start conversations with things like "what startup do you work for"
Re:Girl Tickets to ng-conf on Tuesday September 17, 2013 @02:35AM (#6397920)
Pretty not psyched about the gender normativity.

"If you don't look like our idea of a girl, we'll throw you out of our conference for identifying as one."

Re:Starlite on Tuesday September 17, 2013 @02:31AM (#6397901)
This would make for a great mystery novel.
Bucket Brigade is a better term for this kind of attack. Non-gendered speech and all.
Re:Yahoo reveals its new logo on Thursday September 05, 2013 @01:38AM (#6332370)
I'm not sure Yahoo's brand was ready to be logo-ified. They're currently in such a radical state of change that it feels like an impossible task.
Re:Android is for startups on Wednesday September 04, 2013 @08:19PM (#6331409)
I love the point about iteration here, but I think this post is a little bit disingenuous.

The problem with developing for Android as a startup is that baseline reliability is incredibly resource intensive.

If you want your app to work on the most popular few devices, you will still have to spend a considerable amount of time and money testing the different configurations and fixing bugs that have nothing to do with your core functionality.

If you want broad support to address most of the market, you're going to be spending a huge amount of development time tweaking little details of your code. When you fix a bug for the Galaxy S4, it'll start crashing on the HTC One X, and the Galaxy Note will never look quite right.

Iteration is valuable, but iOS lets you build one product and iterate on it, to build for Android, you have to start by building 15.

I was about to add this to Chrome and then it asked for "all of your data on all web sites" which is too much for me.
Re:Why we need real cryptography instead of passwords on Tuesday May 28, 2013 @07:33PM (#5783572)
That's actually a really good question that this post wasn't focused on. What's cool about the key pair is that the only information that is passed around is the signature, which is only valuable for a few seconds. The key itself is never transmitted and so it can never be intercepted.

That's a separate problem from the length of cracking, but an equally important one with regards to security.

Also, it would be pretty hard to remember even a single password that long...

Re:Why we need real cryptography instead of passwords on Tuesday May 28, 2013 @07:15PM (#5783497)
woops! good catch.
Re:Amazon Services Hackpad on Wednesday April 03, 2013 @07:34PM (#5490010)
Great research, but browsing this I got the "Join the conversation" popup every time I changed pages. Super, super frustrating and made me stop reading pretty quickly. Left a bad taste in my mouth about hackpad.
Re:A Difficult Situation on Thursday March 21, 2013 @07:28PM (#5420112)
My email to Jim Franklin:

Hi Jim,

You have a mess on your hands, and I understand how hard it must be at SendGrid today.

I think you've made a defensible move, and it is hard to hold you in contempt for putting your employees and business first.

That said, I'm really disappointed in your response.

For as long as there have been tech conferences, they have been hostile to women. Sexually exclusive language is the starting point for harassment and assault that have been the status quo for the tech industry for decades. (tech isn't alone here, of course)

A woman trying to report these offenses often went completely unheard. The crimes were completely silenced by a community that protected itself with homogeny, and the results are strikingly obvious in the number of women working, participating, and attending conferences in technology.

This deeply-rooted problem is finally beginning to surface, and we're starting to talk about solutions in a productive way. PyCon was at the forefront of that as they worked incredibly hard to make women feel accepted. Their no-harassment policy and work to get more women speaking and attending represent a huge amount of progress.

It has been a very public effort by the conference, and the results were impressive. A huge number of women showed up to a space they thought would be more welcoming.

Of course, it wasn't perfect. Though we've made a lot of progress, there's still a long way to go before we'll get rid of exclusive attitudes towards women.

What's really disappointing, though, is that when a woman at this conference felt uncomfortable and made her discomfort public, she lost her job.

Her peers, our technology community, responded to her statement with incredible hostility. Threats of rape and murder were abundant yesterday, and we attacked a woman for expressing her discomfort publicly.

Some people, like yourself, said that it would be okay for her to express her discomfort privately, but that the publicity is what made it a problem. But in doing so, you're asking her to give up her voice. You're asking her to stay silent about an incredibly serious problem.

All she did was report factual discomfort publicly. She didn't lie or slander.

And now she's lost her job for it. The message is obvious: women aren't allowed to report misconduct like this. We don't want to hear about the sexual misconduct in our community. A woman's discomfort is her own problem, not ours.

That's the wrong message.

Re:Why Yahoo's Decision Might Not Be So Wrong on Monday February 25, 2013 @03:36PM (#5281599)
good catch, thanks!

Older »