Oh sure, this it can work on, but a proprietary/non-federated E2E encrypted mechanism for Gmail emails alone is out of the question.
Email Markup in Gmail
61–70 of 113 posts
Re: Email Markup in Gmail
#62Earlier quoted context omitted.
Why can't you? I mean, their examples in the link even show how to implement this with a simple Google Apps Script project.
Huh, this has been available for a while so I actually didn't realize this was a new announcement. I was hoping the registration would be less strict if you're only sending within your own domain, but this is good enough really.
It is. You don't need to register if you are sending from your own domain to your own domain.
Re: Email Markup in Gmail
#63From their form: Is your email Promotional or has a Promotional Intent or is a Sollicitation?
I like how you can answer both "no" and "yes" so that they will manually review.
Re: Email Markup in Gmail
#64Earlier quoted context omitted.
ProtonMail may not be the best choice if you're a stickler for standards. Their service unapologetically works only within ProtonMail. Send an e-mail to someone with a different provider and they get a link to a https view of the email.
For encrypted emails, yes. Not for regular emails. They don't support PGP (Does Gmail?) at the moment, but are apparently working on it. What other approaches are there?
>Does Gmail?
Sort of, with a Chrome extension: https://security.googleblog.com/2014/06/making-end-to-end-en...
(I've never used it)
Re: Email Markup in Gmail
#65Feels like this will get (over|ab)used by the same people who have already done it with email newsletters and promotions.
I google search for "birthday gift for mom" and now some retailer who has already emailed me a similar promotion will get that in the top of my search results? Meh.
Re: Email Markup in Gmail
#66Earlier quoted context omitted.
It's only "open" in that they detail the spec they've come up with. Email has been so useful and resilient only because it's an open standard which is broadly agreed on and adopted. Once the big players start adding custom features on top of existing protocols we start seeing fragmentation and parts of the market being cornered off. Once people start depending on this custom functionality, the vendor usually starts r…
You're talking about some kind of neoliberal openness, where open means "the big players agreed to it and it conforms to political ideas about structure". That's not my definition of open. My definition open is you can access the spec for free without limitation, and use, modify, and redistribute it as you see fit. If I am feeling grandiose I will concede that openness requires not just access, but easy access and us…
Having a hard time parsing your objections.
The standard is http://json-ld.org plus https://schema.org. Client developers could freely implement it. It's a W3C standard. But don't modify it just because you can – standards don't like that.
It's annoying that google doesn't activate it for everyone, but that's like complaining about browsers allowing adblockers or SSL root certificates being tied to requirements.
Re: Email Markup in Gmail
#67Earlier quoted context omitted.
Yes, it's really unfortunate. I tried using this for mail sent to myself before but it didn't work.
you should be able to get it to work without approval sending to @X.com from @X.com iirc.
I think it's only Y@X.tld to Y@X.tld that works without applying.
Re: Email Markup in Gmail
#68(self-link)
When this first launched, we found the technical docs for integrators to be a bit lacking, so wrote this up: http://blog.meldium.com/home/2014/5/19/setting-up-gmail-inbo...
It's Rails-centric, but will likely be helpful to integrators in other languages. Hope it's helpful!
Re: Email Markup in Gmail
#69Earlier quoted context omitted.
It's only "open" in that they detail the spec they've come up with. Email has been so useful and resilient only because it's an open standard which is broadly agreed on and adopted. Once the big players start adding custom features on top of existing protocols we start seeing fragmentation and parts of the market being cornered off. Once people start depending on this custom functionality, the vendor usually starts r…
You're talking about some kind of neoliberal openness, where open means "the big players agreed to it and it conforms to political ideas about structure". That's not my definition of open. My definition open is you can access the spec for free without limitation, and use, modify, and redistribute it as you see fit. If I am feeling grandiose I will concede that openness requires not just access, but easy access and us…
How could you modify this schema and expect it to work with the other players?
Re: Email Markup in Gmail
#70Earlier quoted context omitted.
For encrypted emails, yes. Not for regular emails. They don't support PGP (Does Gmail?) at the moment, but are apparently working on it. What other approaches are there?
Not in the web interface, no. But you're free to use any client with GPG support – the beauty of open standards. There should also be browser plugins that add it to the web interface.
I wonder ... can you use javascript in HTML email ? Why not just include a PGP client ? You'd still need your key but why not make a standard for that ?