11–20 of 52 posts
Earlier quoted context omitted.
We were creating a chrome / firefox extensions to manipulate the gmail UI, the project was unrelated to email protocols (but I understand the snark ;-) )
The snark was uncalled for, so is drawing noses on emoticons.
We used this for a project before, just be aware that the DOM changes regularly for gmail, and if an API you rely on breaks you will be SOL until someone fixes it.
It's open-source, if you rely on it, fork it and fix it yourself.
If it's acceptable that it breaks often then it's fine to use, but if you're expecting reliability, then no.
We used this for a project before, just be aware that the DOM changes regularly for gmail, and if an API you rely on breaks you will be SOL until someone fixes it.
It's open-source, if you rely on it, fork it and fix it yourself.
Earlier quoted context omitted.
The snark was uncalled for, so is drawing noses on emoticons.
They are also running into this issue: https://xkcd.com/541/
> Linux (or BSD [U+1F642]) would
EDIT: Does HN not support emoji?
EDIT^2: How it should look: https://pastebin.com/raw/rKmTCdFX
We used this for a project before, just be aware that the DOM changes regularly for gmail, and if an API you rely on breaks you will be SOL until someone fixes it.
You kind have the same problem if you are the only one using your custom lib and you dont have a huge army of others who could fix it. And it's… so… much… more exhausting
InboxSDK (from Streak) is the best API to use for Gmail.
InboxSDK (from Streak) is the best API to use for Gmail.
I personally found both to be lacking in different areas, too bad they weren't merged together to cover a broader base.
Earlier quoted context omitted.
It's open-source, if you rely on it, fork it and fix it yourself.
The issue is that gmail will update at anytime, without warning, so there will always be a period when your service will break. And you need to have unit tests running often to figure out when it breaks, and have a dev on call 24/7 to ensure a speedy fix. This is a universal problem with extensions targeting website DOM's, but worse if you have an SaaS product that has an SLA.