All the logic happens at the back-end level via our API communicating with Gmail's one. Nothing is done on the client-side (i.e., extension) besides the integration of our buttons/features within Gmail's UI.
The RSA key is just used to show that what has been inserted was through our service. Note that the final hash resulting from the mixer is done without any RSA.
EDIT: reply to your last comment. The whole idea is to propose a "hybrid" architecture that bridges the gap between a centralized technology such as the Email with the benefits of a decentralized one, the blockchain.
This hybrid process implies you will need to trust parties at some points, e.g., Google and Gmelius. However, the point here is to offer a means to store in a robust way the trace that a specific email communication existed at a point in time, including its context/content.
Yes, we integrate with Gmail and communicate via the official Gmail API.
We only receive response statuses and act accordingly. Moreover, we think it's important for this functionality to make sense to insert the hash corresponding to the integrity of the email, and so make possible for our customers to "prove" they have indeed sent an email with a specific body/subject/...
Hi vivan. Thanks for your comment. Besides the signature of an email using the robustness and persistence of the blockchain, what is different with "Email Stamping" and especially interesting for professionals who send sensitive emails (e.g., lawyers, insurers, brokers...) is that they have a way to show they sent an email with a specific content at a specific time.
A decisive challenge raised by today’s email dominance in the workplace is that the latter means of communication does not offer a built-in function to prove the integrity and authenticity neither of its content nor of its origin. Knowing that emails are increasingly presented as legal evidence in courts worldwide, it becomes urgent to think of approaches that could palliate the inherent flaws of email.
EDIT: And yes, Gmelius offers a lightweight CRM targeting SMEs that covers all the stages of the modern communication flow: from the first interaction to the potential signature of a contract/quote. Besides, Gmelius offers a shared inbox making possible to follow-up on leads, stay in sync with your team.
Hi! Regarding your tracking remark, companies such as YesWare, MailTrack, MixMax (and so on) use pixel trackers. While such trackers are indeed made available through a Google proxy, the caching is overridable if you pass a no-cache header (http://blog.movableink.com/real-time-content-and-re-open-tra...).
The Inbox SDK makes easier the interaction with Gmail's UI and does not transmit or index data.
Thanks for your comment. When a user enables the feature that homogenizes the look of incoming emails w.r.t. its Gmail theme, Gmelius will not modify the style of well-formatted HTML emails (e.g., invoices, newsletters, etc.).
In addition to our "email scheduling" feature, email follow-ups and reminders will be soon available as well. With the latter features and other ones Gmelius currently offers (e.g., To-do App, email trackers detection and blocking, email templates), I'm sure your will find a place for Gmelius in your browser...
If you need more convincing, just go through our code after installing the extension and/or check your console and network when using Gmail with Gmelius installed.
Great job and initiative! Gmelius Founder here. A few questions:
i) Are you planning to make the whole implementation Open Source?
ii) Say I wish to adopt and use your SDK in my current Gmail/Inbox extensions (>100K daily users), may I expect the implementation of a fixed upper limit on the number of transmissions in the coming months (which could endanger the reliability of my service for my users)?
iii) While the SDK currently only focuses on the UI, are you planning to add more "complex" interactions, such as Gmail filters/Gmail preferences ? If yes, feel free to get in touch. I will be happy to help.
This is an early (beta) version of Gmelius for Google Inbox, currently available as a Chrome extension. Feel free to share your suggestions and feedback. Thanks in advance!
The RSA key is just used to show that what has been inserted was through our service. Note that the final hash resulting from the mixer is done without any RSA.