Live data from Hacker News

Email Markup in Gmail

developers.google.com

51–60 of 113 posts

Re: Email Markup in Gmail

#51
post #46
post #8

This is a bad thing. Gmail needs to be e-mail and nothing more or this is EEE.

I totally agree. Besides, what is wrong with HTML? And why doesn't it render properly in the gmail client?

HTML is semantically poor, so if they implemented this features in it, they'd have to use stuff like Google-specific links for the actions.

This way they can use a more data-friendly format created and supported by multiple organizations (Schema.org), which any client can use freely.

As a non-Gmail user myself, I'm quite happy with their choice, since it means I can make it work with my client and my calendaring software.

Re: Email Markup in Gmail

#52
post #24
post #2

Note that this only is available to high volume senders ( https://developers.google.com/gmail/markup/registering-with-... ): > Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least.

I have a very small SaaS and I was approved. I don't send hundred of e-mail to other e-mail addresses daily, but I do send a lot of e-mails to myself (server alerts and notifications). Approval process is very easy and takes 2 minutes, it is worth applying.

Can confirm. Sending a few hundred emails per day, got approved. Customers like it.

Also, this is an old thing already. I thought everyone had seen this in their gmail!

Re: Email Markup in Gmail

#53
post #18

Earlier quoted context omitted.

Why can email not evolve? Structured data in markup works well on the web. It's open and could be implemented by any client.

It's only ever going to work for gmail users. For people who read their email in text-only clients this will never do anything. You know, people who use serious email, not to send pictures of balloons and 96-pt Happy Birthday in pink on purple text.

It's great to see that there aren't just "serious" notebook users ("this may be great for digital artists, or journalists or teachers but I'm a /serious/ professional and that's why I hate Apple").

Now there's "Serious" email, and if you don't read your email on the cli, you're just an amateur easily impressed by shiny toys.

Can't make this stuff up... Or, you know, that structured data and semantic markup are excellent for any number of "advanced" uses.

Re: Email Markup in Gmail

#55
post #37

Earlier quoted context omitted.

Then please extinguish email, Google. I would guess that something better would take its place. The only danger is that some proprietary service sucks it all up.

What, you mean some proprietary service like Gmail?

No, proprietary service like Facebook messenger

You know, incompatible with anything else, with not even API access, no third party clients and Facebook as the ultimate arbitrator of your ability to reach anyone (including your customers).

Re: Email Markup in Gmail

#56
post #32

Earlier 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?

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.

Re: Email Markup in Gmail

#57
I kinda like this. Some big players are adding these to emails, and you can easily add the parsing to a third-party client (Inbox, where this appears in, hurts my head so I refuse to use it)

Re: Email Markup in Gmail

#58

Earlier quoted context omitted.

A good free one?

If you rely on email, it's worth paying for. I'm a paying Fastmail customer, and it's worth every cent.

I'm paying as well for my personal account.

But, I am having a hard time justifying switching my entire family over. A family of 4 is $20/mth, that's 25% of the cost of my internet connection and seems rather steep.

Re: Email Markup in Gmail

#59
post #18

Earlier quoted context omitted.

It's only ever going to work for gmail users. For people who read their email in text-only clients this will never do anything. You know, people who use serious email, not to send pictures of balloons and 96-pt Happy Birthday in pink on purple text.

It's only ever going to work for gmail users. For people who read their email in text-only clients this will never do anything. Why not? If anything, this should been a boon for us text-only client users, since the metadata is structured in a format that can be easily parsed and displayed in an appropriate way, instead of having to deal with HTML conversions. Having a key shortcut on Alpine to activate the main email…

I completely agree. Having a more semantic structure rather than "anything goes" HTML can only be a good thing for the state of emailing in 2016.

Many high profile websites don't even bother sending a text/plain alternative with their emails anymore and the HTML is often cryptic when viewed from a text browser. Anything that can improve this is a good thing.

I do have a minor beef with this implementation however: at first I assumed that this metadata would be stored in custom email header (X-Mail-Action or whatever) but as far as I understand it's embedded in the HTML instead. It would make it more painful to add support for that to existing clients, especially if they use external tools to display HTML.

Re: Email Markup in Gmail

#60

Earlier quoted context omitted.

Why can email not evolve? Structured data in markup works well on the web. It's open and could be implemented by any client.

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 usability by all stakeholders. That's a little radical, but the point is just that there's a degree of accessibility implied in the above. If you have to crawl through a snake pit to get the source perhaps that's not really open.

But your definition, which requires buy-in from Oracle and PepsiCo in order to be "open"... I think I reject that definition.

Post reply on HN