poutine

13 ms·

121.
by poutine 13y ago
You've described OAuth in part with its refresh and access tokens.
122.
by poutine 13y ago
This is not arbitrary at all and has definition by industry standards. Passwords are used by people. Keys by machines. This requires different security policies. Passwords will have complexity rules and shorter expiration policies such
123.
by poutine 13y ago
As an API and security professional I've found to be secure and performant one should do the following with APIs: - Dont listen on HTTP, force HTTPS (Tune your ciphers! see https://www.ssllabs.com/ssltest/index.html ) - Ensure that any cli
124.
by poutine 13y ago
This isn't a problem specifically with HTTP basic which at the end of the day is just a HTTP request header with an encoded string. If you're using basic auth and a long random server generated key as Stripe does instead of a user supplied
125.
by poutine 13y ago
You also hash the two differently in your database. With passwords you want to bcrypt (or similar) them to protect against exposure of the DB and an attacker brute forcing the hashes. Since this is virtually impossible for long random str
126.
by poutine 13y ago
Seems a bit of a bother to use chopsticks and the fishing line contraption. Since it's to test what the user experience is just get another person to watch the users gestures and click or touch the computer that's powering the display to t
127.
by poutine 13y ago
Thank you. We're considering a self installed version but it'd be a large enterprise type install and further in the future.
128.
by poutine 13y ago
You can see pricing here once you login: https://admin.telemetryapp.com/account/plan We're going to put pricing on the public site too. We plan to stick around of course, the major advantage for us is that this project has almost no b
129.
by poutine 13y ago
Yep, I need to make that demo board more dynamic. The technology is such that we can easily update once per second, perhaps even more frequently with some animation changes. Server sent events makes things easy.
130.
by poutine 13y ago
Oops, forgot to include the link to our OSX desktop app as per the parents request, you can get it at: https://itunes.apple.com/ca/app/telemetry/id571033468?mt=12
131.
by poutine 13y ago
Telemetry is just in the process of getting going. The capabilities you talk about are coming within the next couple weeks to Telemetry (I'm one of the two lone programmers behind Telemetry). Right now the app is uber geeky but we've ma
132.
by poutine 13y ago
http://www.telemetryapp.com
133.
by poutine 14y ago
It's on their Twitter account too.
134.
by poutine 14y ago
Exactly. Penn and Teller did a bit on it too: http://www.youtube.com/watch?v=2bwGsOBTlhE So fucking what, indeed.
135.
by poutine 14y ago
Agreed. Not defending pci. Nevertheless some qsa is going to get their panties in a twist if their scanning tool goes red.
136.
by poutine 14y ago
BEAST causes PCI scan failures from the major scanning vendors. Therefore it's a significant practical issue for any site taking credit cards. Try the https://www.ssllabs.com/ssltest/index.html scan and you'll see what it thinks of your
137.
by poutine 14y ago
I've been using the beta to navigate around Vancouver for a month or so and it works quite well. Turn by turn with voice commands through bluetooth to my car is great. The Yelp integration is pretty useful too. Big thing that's missing is
138.
by poutine 14y ago
Safari in 10.8 works in a similar way as Chrome does with the address bar. Indeed it seems to be faster too, I'm toying with switching from Chrome. We shall see.
139.
by poutine 14y ago
737's don't go that fast at sea level. Air is too dense. An f4 could probably go 2-3x as fast as a 737 at any altitude. I'm too lazy to look up the specific values. As to why they used an f4? Probably a heck of a lot cheaper than a 737 at t
140.
by poutine 14y ago
I listened. Kinetic energy is the mass times the square of the velocity. F4's go way faster than 737's. Thus kinetic energy is comprable between the two. On the second point: http://en.wikipedia.org/wiki/Containment_building "The conta
141.
by poutine 14y ago
"Probably not much" to answer your real question: http://www.youtube.com/watch?v=--_RGM4Abv8 The US government has done the test, granted an F4 isn't a passenger jet but it probably has similar kinetic energy to a smaller passenger plane
142.
by poutine 14y ago
Heh, welcome to the learning curve :) Yeah, it can be ugly, but once you know what's going on it all reads pretty quickly.
143.
by poutine 14y ago
- No Interface builder. Really a big loss given the power of Storyboards/segues, layout of objects, complex flows. - No syntax/error checking as you type - No static analyzer - No code completion (perhaps you could find a 3rd party module
144.
by poutine 14y ago
Because I wanted to? It's the Internet.
145.
by poutine 14y ago
- Objective-C is Hard to Use It has a much steeper learning curve than Ruby for sure, but once you're proficient it's no harder to use. Indeed there's benefits to both languages. - Xcode is Unstable It's gone through periods of instability
146.
by poutine 14y ago
Not case closed. Given that you lose a lot of useful tools (Interface Builder, Storyboards and such) and that Objective-C can be pretty quick to code with Xcode I would contend that given expertise in both a complex application would take
147.
by poutine 14y ago
You need to keep in mind that you don't actually type out the entirety of XCode's methods. For instance: self.window = [[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]]; Was about 45 key presses in Xcode. And this is a fairl
148.
by poutine 14y ago
REPL seems to be a crutch for not having a visual interface builder. His example in the video wouldn't have been an issue in Xcode as you'd have positioned and named the label correctly to begin with, and would have seen it in context too.
149.
by poutine 14y ago
As a long time Ruby and Objective C developer who loves both languages I'm not impressed. Sure the REPL stuff is neat, but I would position my UI elements correctly in interface builder to begin with. I'm also not keen on typing out the co
150.
by poutine 14y ago
Yes, pretty much this is how I've been doing JSON API's for a couple years now. Making things all about convenience and ease of use for the API consumer, that's really what an API should be about. Afterall, API's are UI for developers.

More ›