Recovered video: https://www.youtube.com/watch?v=CjZ33C9JZTM
4,593 karma · joined April 21, 2010
http://mikeknoop.com https://x.com/mikeknoop
Recovered video: https://www.youtube.com/watch?v=CjZ33C9JZTM
Any particular goals you want to achieve with this project?
On top of that, donations trickled in for months after from folks who didn't originally pledge.
The XDA community is very good about these things.
I love the use case "When I scan a business card, automatically invite them on LinkedIn to connect". Then I can toss the card guilty free.
We installed statsd/graphite early on to experiment around with visualizing our task and request logs for Zaps. We've since settled into Elasticsearch and Graylog which is phenomenal for debugging and support -- but has it's growing pains.
The timeseries stuff is used more at the application layer, rather than the pure logging layer. For example, I believe we're using it to track how many tasks an account has done over the last 30 days for pricing/plans.
In fact, my very first web server was going to be hosted by him. I recall sending him like $30 in the mail to host it way back when I was young enough to not even have a bank account yet.
Learning how to give a better talk is just a proxy for: how can I better communicate my ideas to the audience so they remember them?
In 2 months no-one is going to remember any of the details about your talk but they'll remember the experience and if you have resources online, they'll seek those out.
I was under a time crunch to memorize my talk (I think I started about 4-6 hours before) so the sentences were a way to speed that along.
The process went like this:
1. Read talk end to end out loud from sentences
2. Start trying to time sentences with slides (with sentences still there)
3. Remove sentences but see all the slides still
4. Only see the current slide
Took me about 2-3 hours to nail down. By step 3 and 4 I was already improvising most of the sentences each time though and only the core point stayed constant.
It's huge (4,000+ words) but if you ever give a talk it could be really useful.
It uses the awesome HNSearch API to poll for new mentions of phrases and triggers a Zap whenever it finds one. (I have it send me an SMS).
Here's a better, more direct Zap Template: http://zpr.io/gsjS
If you pick Backbone, you'll be inventing a lot of patterns yourself and scaling it, but I think that appeals to a lot of people.
1. Webhooks
2. A subscription layer via REST
Several major players already are doing this but it doesnt have a name.
REST Hooks are a way to consolidate that momentum and push it to a broarder audience.
Here are more resources:
Intro: https://zapier.com/engineering/introducing-resthooksorg/
EDIT: here is the screenshot: http://zpr.io/6SmC.png
Integrations are of course limited to what can fit inside the "trigger/action" model. However, most of the first-party Glass apps take advantage of Glass in about the same way and you can't extend them like you can with Zapier.
Glass is also a bit limited in how you can consume content. Right now you can read content from Gmail (only one inbox), SMS, CNN, New York Times, and maybe a few others. With Zapier you can push any content you want to the device in any format and filtered in any way.
Some of my favorite use cases while building the integration:
1. Take a photo on Glass -> Upload to Dropbox
2. Send RSS headlines to Glass, when I "share" a headline and add a caption -> Send to Buffer
3. Set up event reminders inside Google Calendar -> Send reminder to Glass when the event is about to start
All said, I'm super excited to see what others start building. Not just developers (we've had access to the Mirror API already) but what real users want to use Glass for.
Zapier users constantly blow me away with their creativity and given an open-ended device like Glass, I'm sure we'll see some super creative use cases.
Given that, I'll propose a 58th: be formidable enough to overcome any of the other 57.
Based on my experience, each team individually deals with quotas for their API. Google Tasks is not really a dedicated product so it probably has little to no permanent team behind it. This is probably the cause for the slow response time on quota requests.