Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
michaelfairley
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
michaelfairley
14y ago
Our webapp doesn't directly communicate with photon at all. The webapp sticks the photo in a certain bucket on S3 with, and then includes the path to that photo in the photon url that gets passed to the client. On the read path, HTTP is rea
62.
▲
by
michaelfairley
14y ago
We do two layers of caching (CDN in front of Varnish in front of photon). The latency is annoying, but it's no worse than serving the files directly off of S3 (as we were doing previously). In an ideal world, Photon would be running on boxe
63.
▲
Processing photos on demand with Photon
(blog.1000memories.com)
51 points
by
michaelfairley
14y ago
|
15 comments
64.
▲
Context switches and serialization in Node
(aphyr.com)
4 points
by
michaelfairley
14y ago
|
0 comments
65.
▲
by
michaelfairley
14y ago
We used to have a horizontal quilt[1]. We got rid of it both for design reasons, and because the math behind it is much trickier and limits the layout (e.g. you can't do arbitrary ordering of the photos). 1: http://www.iftf.org/system/file
66.
▲
Open sourcing the “quilt” view for iOS
(blog.1000memories.com)
56 points
by
michaelfairley
14y ago
|
14 comments
67.
▲
Monorail (n., jargon)
(somethingsimilar.com)
1 points
by
michaelfairley
14y ago
|
0 comments
68.
▲
by
michaelfairley
14y ago
# of low-quality support requests could work for that.
69.
▲
by
michaelfairley
14y ago
Have you ever A/B tested picodollar pricing agains full dollar pricing?
70.
▲
Guy Steele - Growing a Language
(organizedwonder.com)
6 points
by
michaelfairley
14y ago
|
0 comments
71.
▲
Why I don't like factory_girl
(blog.steveklabnik.com)
2 points
by
michaelfairley
14y ago
|
2 comments
72.
▲
The lady in the taxi – a parable of metrics
(dannorth.net)
2 points
by
michaelfairley
14y ago
|
0 comments
73.
▲
Why there are Datacenters in NY, Hong Kong, and Tokyo?
(perspectives.mvdirona.com)
4 points
by
michaelfairley
14y ago
|
0 comments
74.
▲
Hidden Government Scanners Will Instantly Know Everything About You
(gizmodo.com)
7 points
by
michaelfairley
14y ago
|
1 comments
75.
▲
On Resilience in Automated Systems, Failures and the Human Factor
(paperplanes.de)
5 points
by
michaelfairley
14y ago
|
0 comments
76.
▲
Don't Make Your Code "More Testable"
(gmoeck.github.com)
4 points
by
michaelfairley
14y ago
|
0 comments
77.
▲
by
michaelfairley
14y ago
Ultimately, OP's strategy is just increasing the cost of brute forcing. Why not use the cost increasing features built into the hashing algorithms themselves?
78.
▲
by
michaelfairley
14y ago
_Nobody_ is hashing thousands of passwords per second as part of a typical webapp load. Even if somebody was, they would need only ~50 cores for hashing. I'm sure anybody with that much traffic could easily shell out a few thousand bucks fo
79.
▲
by
michaelfairley
14y ago
Or just use bcrypt/scrypt/PBKDF2 in the typical manner. You're much more likely to screw yourself by mis-implementing this than you are to actually gain any real security benefit from it.
80.
▲
Siren
(github.com)
1 points
by
michaelfairley
14y ago
|
0 comments
81.
▲
Coda Hale: The Other Side of Software Engineering
(livestream.com)
3 points
by
michaelfairley
14y ago
|
1 comments
82.
▲
Why I love Code and Coffee
(blog.apprentice.us)
1 points
by
michaelfairley
14y ago
|
0 comments
83.
▲
Fdoc: Square's API Documentation Tool
(corner.squareup.com)
2 points
by
michaelfairley
14y ago
|
0 comments
84.
▲
It’s not called “Red Green Red Green Red Green Spend A Whole Day Refactoring”
(devblog.avdi.org)
2 points
by
michaelfairley
14y ago
|
0 comments
85.
▲
"X-" deprecated for HTTP headers
(tools.ietf.org)
133 points
by
michaelfairley
14y ago
|
35 comments
86.
▲
Client v. Server Templating Shootout
(ryanflorence.com)
1 points
by
michaelfairley
14y ago
|
0 comments
87.
▲
Clojure: Production Web REPL
(blog.jayfields.com)
3 points
by
michaelfairley
14y ago
|
0 comments
88.
▲
Tap versus intermediate variables
(naildrivin5.com)
1 points
by
michaelfairley
14y ago
|
0 comments
89.
▲
by
michaelfairley
14y ago
It's now yellow with this: "9:27 PM PDT We continue to investigate this issue. We can confirm that there is both impact to volumes and instances in a single AZ in US-EAST-1 Region. We are also experiencing increased error rates and latencie
90.
▲
by
michaelfairley
14y ago
Definitely an EBS issue. Our (EBS backed, Heroku hosted) DB was returning queries more and more slowly leading up to the outage.
More ›