1,178 karma · joined August 28, 2010
(Adding a credit card didn't let us increase the cap.)
When we have user accounts and other things like that, we'll have to think about how to do that the most reliable way as well, which may be Redis or may mean bringing Postgres into the mix. I think there's a lot of benefits to keeping the variety of technologies down so if we were to bring in another, it would need to offer something compelling that our current mix doesn't offer.
The major theme we were trying to highlight in this post is just how far Redis can take you if you're trying to build a component-based backend and need a way to handle the communication as well as the state of the system.
The other cool thing that Filmgrain captures that's different from quality is insight into what people liked about a movie afterwords. For example, people were divided on if Great Gatsby was good or not, but people couldn't stop tweeting about the soundtrack. I'd have never known how much people cared if it wasn't for this feed and it's this type of meta information we want to bring forward, as we can.
The problem is Google never really took it any further and stopped supporting it. Classic example of a project that simply withered without any love.
I haven't messed with weekly active users, for example, because my sample space of time is so small I couldn't really make any statements.
The other thing I take as a good sign is that the number of registered devices has officially overtaken the number of registered users, meaning people have taken the time to register more than one device more often than not even registering one.
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 evening, I realized that as an extension, any ajax request I make will have access to the same pool of cookies as normal browser requests, so it turned out that if a user is logged in on the site, they're automatically logged in on the extension, too.
This made everything SO much easier, but I had wasted like 8 hours of work to get there :)
I had a couple friends I told about it and I'm sure they upvoted the submission, but I think really I did well because PushBullet is exciting to Android users and r/android is a hotbed of people looking for exciting things to do with the devices they know have a ton of potential.
I've set up an account and am leaning toward SendGrid right now since I dont need an SMTP server as MailGun requires.
Am I wrong about that, btw? It's all new to me. (I use Google Apps for Gmail, etc. and MailGun wants the email dns stuff which is a problem.)
I'll figure something out, I work full time so I can manage the costs without noticing but that isn't an answer so much as a deflection :)
The app receives the tickle and makes a quick api call for the push data and sees it needs to get a file. It then asks for the file and I make sure they have permission to download it and then let them.
Over engineered? Maybe :)