I love social software and interesting data.
I'm 29. I love cooking and trying new food.
I live in Brooklyn, NY Bayonne, NJ.
Contact me at david.lifson@gmail.com.
I'm the co-founder of Postling, a unified dashboard for small businesses.
It's important to me to give back to the startup community, so if you are interesting in hearing my thoughts about your startup, sign up for my office hours or send me an email.
My other sites:
Tumblr Uptime (http://tumblruptime.icodeforlove.com/)
This page provides you with Tumblr’s current API status. The API method’s are checked every 15 minutes for valid responses, and are benchmarked.
It’s interesting to see some benchmarks in a visual way after spending time with Tumblr’s API. Both the /api/delete and /api/read methods, according to this, have a 15% uptime. Meaning if you’re relying on this API for anything you build, your tool will likely only work 15% of the times it is loaded. And that’s not even touching the high latency you’ll come across working with it.
Between a 15% uptime, a terribly slow response and a bunch of missing features, is it any wonder that we’re not seeing any real innovation on the Tumblr API?
Note: data is only from the last 24 hours. Not that it makes things OK. When most companies talk about many 9s of uptime they have (99%, 99.9%, 99.999%), here we have 15%. Awful.
I released an API for Tumblr Uptime today, feel free to use it.
Now who wants to build something??
This has definitely been a problem for me lately. I run a small side-project called trntbl that lets you listen to...
Note: data is only from the last 24 hours. Not that it makes things OK. When most companies talk about many 9s of uptime...