EvanHahn's comments

On: I made a little audio speed calculator

[EvanHahn]

hell yeah. get his ass

On: How I build software quickly

[EvanHahn]

Of all the comments the post received, this one meant the most to me. Thank you.

On: My failed attempt to shrink all NPM packages by 5%

[EvanHahn]

Yes: https://github.com/npm/pacote/blob/bf1f60f58bb61f053262f5472...

On: Go-Safeweb

[EvanHahn]

Helmet author here. This is a similar project, but not the same.

Helmet covers HTTP response headers, and that's it. This project seems to have a wider scope, covering things like auth and error handling.

[efilife → EvanHahn]

Your last comments were 10 months ago and 10 years ago. A rare occurence. HN at its finest

On: How to delete your data from data brokers

[EvanHahn]

Another deletion service I like that the article didn't list: <https://www.kanary.com/>

On: Show HN: Use any text as a domain name

[EvanHahn]

The first thing that came to my mind when I saw this: hash collisions. Could problems arise from two keywords that hit the same domain?

Really cool idea, though.

[dionyziz → EvanHahn]

If you find a hash collision, let us know. As security people, we'd be very, very concerned if you can find even one collision or even engineer a collision in SHA1 or especially SHA256.

[primitivesuave → EvanHahn]

With SHA1 the chances of that happening are so close to zero that you'd have to create trillions of keywords before you even approach a minuscule chance of hitting a collision.

One of my favorite analogies for SHA collisions: http://stackoverflow.com/a/4014407/690258