Guzba

12 ms·

91.
by Guzba 11y ago
This almost certainly isn't true, it's far more likely you've only noticed it when it worked. Every other time, when it didn't, the comments were buried at the bottom of the article.
92.
by Guzba 11y ago
I work on an extension for Chrome, Opera, Safari, and Firefox that's pretty widely used. Firefox (Jetpack) is so different from the rest that I basically hate working on it. I get that some people may love XUL and whatever, but having
93.
by Guzba 13y ago
Nope, we just let you add friends in the app from your contact list. (If you add them, then we do get their name and email so we can put them on your friend list.)
94.
by Guzba 13y ago
We have a plan for earning revenue but haven't deployed it yet. This feature furthers our vision for notifications as does the rest of our service. We'll be focusing on revenue soon but right now we're focused on growing sinc
95.
by Guzba 13y ago
(Dev here) You've got the basic idea. We do everything over https of course, but you are still sending your data through our servers.
96.
by Guzba 13y ago
This is great. I totally did that on purpose (lining it up vertically and everything) but I figured I'd never hear anyone comment on it :)
97.
by Guzba 13y ago
Using GCM for Chrome is free but you do have to have an API key (unlike some Google services). The 10,000 messages cap is is what they call a courtesy limit, hinting that you can get it increased, but we had never gone through the process o
98.
by Guzba 13y ago
This is all true, and HTTP really is a great choice, but that's the point I'm trying to make--it's a choice and there are alternatives. Specifically for mobile apps, those alternative are really attractive.
99.
by Guzba 13y ago
Websockets are the natural choice when/if we bring Filmgrain to the browser. I actually think Websockets are really exciting, but for a mobile app just going straight socket made more sense.
100.
by Guzba 13y ago
Web sockets are great for getting TCP in the browser but since we're only building mobile apps right now, we don't need the HTTP layer, instead we're using straight sockets.
101.
Building a TCP API: How we built our realtime app, Filmgrain, part 2(blog.filmgrainapp.com)
18 points by Guzba 13y ago|20 comments
102.
by Guzba 13y ago
Right now we don't have user accounts or anything mission critical to store. (Everything we use Redis for right now is essentially app state and we use it to managing cross-machine communications.) When we have user accounts and other
103.
by Guzba 13y ago
Why do you think that?
104.
by Guzba 13y ago
When we started working on Filmgrain, what became clear was that it wasn't so much that the popularity told you if the movie was good or bad, it was that it worked remarkably well at highlighting the movies people care about right now.
105.
by Guzba 13y ago
Thanks a lot. Also, it's definitely possible an iOS app is already in the works :)
106.
by Guzba 13y ago
I actually built this with two friends and our goal was to build something together and play with realtime in an app. As far as our plans, getting this far feels great and we're excited to see how people feel about the app. If people l
107.
by Guzba 13y ago
Here's the launch blog post, too, if you're so incline. http://blog.filmgrainapp.com/2013/06/15/filmgrain-is-live/
108.
Show HN: Filmgrain, a realtime movie + Twitter app(filmgrainapp.com)
19 points by Guzba 13y ago|10 comments
109.
by Guzba 14y ago
No, its not. I just haven't had the time to get that far. It's a hard problem but selling emails isn't an option.
110.
by Guzba 14y ago
I have hey@pushbullet.com on the Play Store for feedback, and yeah I should get a contact page up on the website too.
111.
by Guzba 14y ago
There might have been, it wouldn't surprise me if they were talking about Chrome to Phone, an extension for Chrome they built for pushing to your Android phone. The problem is Google never really took it any further and stopped supporting i
112.
by Guzba 14y ago
Eventually, of course. Right now though I have a ton on my plate as it is and zero iPhone experience :)
113.
by Guzba 14y ago
Glad you like the app! And the Chrome extension will pre-fill for the page you're on, but not for tabs you had open before you installed the extension :)
114.
by Guzba 14y ago
I agree with your assessment that active users is the only count that really matters. I haven't actually got the numbers myself but I watch the split between users and things pushed and it is growing wider every day. This is my proxy right
115.
by Guzba 14y ago
Other than paying for the 'infrastructure', which isn't much yet, I haven't had to spend any money on user acquisition.
116.
by Guzba 14y ago
Actually, I'm using Google's Cloud Messaging infrastructure which means I get the benefit of the same technology Google uses to deliver Gmail notifications, etc. It also means there isn't any incremental battery life harm. :)
117.
by Guzba 14y ago
I'm basically just using it as memached right now. I need to use something since I have more than one app server so storing it in memory on the machines won't work.
118.
by Guzba 14y ago
Basically, its a superset of Chrome-to-Phone functionality that supports newer devices and takes advantage of the new notification features in Jelly Bean. Hope that helps :)
119.
by Guzba 14y ago
Ah, thanks for pointing this out. I'll push the fix as soon as all of this dies down. No need to rock the boat while there's a party :)
120.
by Guzba 14y ago
I really liked this post so I'll share a funny story about the Chrome extension. I spent a couple evenings getting pseudo-authentication working with OAuth to log people into the extension, it was annoying and a real pain. Then, the third e

More ›