kartikt
Joined 14 years ago
Karma
369
Submissions
43
Member since
Sep 11
http://kartikt.com
View on Hacker NewsRecent submissions
Comment · 9 years ago
The original comment is meant as an observation rather than an attack. It's great to see the author of the post use gmail.js to quickly get the sentiment analysis working with 30 lines of code.
The library was a fun side project and has been used by many companies (big and small) over the past few years. Its always nice to see someone make a cool extension on top of gmail.
Here is another one that came out a while ago (uses gmail.js) and on the same theme as this original post:
http://www.slate.com/blogs/xx_factor/2015/12/29/new_chrome_a...
Comment · 9 years ago
lol
Comment · 10 years ago
Thank you for the kind words!
Comment · 10 years ago
Creator of gmail.js here - please see my comment to nathancahill on this thread :-)
Comment · 10 years ago
Creator of gmail.js here - thanks Nathan! I started working on this almost 3 years ago for a personal project. At that time there weren't many libraries available to work on top of gmail so I decided to compile all the helper functions into a standalone library hoping that after it goes on github, others might contribute.
After I did a Show HN in late 2013 a lot of people expressed interest in using this and ever since then, gmail.js has been used by a lot of individuals and startups. I'm really happy that people still frequently contribute to the library by adding features and/or reporting bugs and it has definitely gotten stronger and more stable over the past year (a very special thanks to Brent Kelly)
As a funny observation, the public sentiment towards gmail's DOM still remains the same as it was 3-4 years ago, and while I agree that it changes quite often, I do believe that the severity of those changes is heavily overstated. The disadvantage of an abstraction layer like gmail.js is that you always have to be on top of the DOM, but gmail.js is at a place where enough people are using it that if some major change occurs to the gmail UI, it'll be reported a lot faster because there is now a community using the library. In the past 3.5 years, only a single DOM change on gmail (about 2 weeks ago) has made a breaking change that affected all users from this library.
The whole thing is intentionally designed to be a single file where majority of the functions are standalone so if something goes wrong, anyone can easily understand how it works! That being said, a lot of the focus of this library is to abstract network events so developers making extensions on top of gmail can fire off events when a gmail user gets a new email, sends email, deletes etc. Those things rely very little on the DOM.
And as always, feedback and bugs welcomed :-)
Comment · 10 years ago
This is primarily designed to make chrome extensions on top of gmail
Comment · 11 years ago
yup!
Comment · 11 years ago
Creator of gmail.js here. Can confirm
Comment · 12 years ago
Adding UI heavy features with that library is going to be painful (especially a whole new tab interface). It's designed for a rather 'active' interaction with emails (I made it). Most of the auto reply algorithmic stuff can be accomplished through context.io
Comment · 13 years ago
People will start switching to Google+
Comment · 13 years ago
I agree. Found this on twitter so decided to post it here.
Comment · 13 years ago
Check out this guy's tweets. So many negative reviews on the internet https://twitter.com/WayTooGosu
Also, the entire site seems to be running on PHP..
Comment · 13 years ago
Hey zrgiu_, there isn't a native observer for that action yet but the closest call is to check if the user is inside an email. I've created a gh issue out of it so hopefully you'll be able to set triggers with the observer method, instead of setInterval