4 ms·
The format may be open, the ability to use it isn't - you need to register with Google[1] or they won't display actions on your e-mail. This appears to be neces
by makomk 14y ago
The format may be open, the ability to use it isn't - you need to register with Google[1] or they won't display actions on your e-mail. This appears to be necessary for security reasons. Imagine if every e-mail provider did the same thing!
[1] https://developers.google.com/gmail/schemas/registering-with-google https://developers.google.com/gmail/schemas/registering-with...
- icebraining 14y agoThat's bad, yes, and I wish they didn't require that, but it doesn't hinder the use of the protocol outside of their services, which is the most important thing. It just adds some extra work to the senders.
- jacalata 14y agoTo hinder: to add difficulty. I'd say it certainly does hinder use of the protocol.
- icebraining 14y ago"doesn't hinder the use of the protocol outside of their services"
- dragonwriter 14y ago> > it doesn't hinder the use of the protocol outside of their services > To hinder: to add difficulty. I'd say it certainly does hinder use of the protocol. How does Google requiring registration before actions are displayed in Google properties hinder use of the schemas in email outside of Google services?
- ars 14y agoBecause just like google needs people to register for security, so do other providers. This rapidly becomes unwieldy - how are you going to convince people to register with tons of providers? So this format is pretty much google only.
- dragonwriter 14y ago> Because just like google needs people to register for security, so do other providers. That's probably a bad assumption, once you have more than a few parties using this system. I'd be surprised if even Google used the current, apparently manually-reviewed, registration system for long rather than as a short-term measure before moving to a less cumbersome accountability mechanism (and this is more "accountability" than "security".) But even if multiple parties were using that kind of method, there's a clear incentive -- especially for the players that aren't Google, but even Google has some incentive -- to build a facility where a shared registration application can be automatically distributed to multiple parties.
- jacalata 14y agoI assumed by "outside of their services" you meant non-google people who want to send email using this. On re-read, you mean it doesn't stop anyone else building a client that can understand these actions, right? That's true.
- gcb0 14y agoAnd even if they implement the "open standard" in outlook, who says Google won't bait and switch (oh the irony) then, like they did with their youtube apps on windows mobile?
- thefreeman 14y agoGive me a break. How is requesting they remove a non-compliant youtube app a "bait and switch". Is this going to be the new "cool" thing to post now every time a submission involves google?
- ChrisClark 14y agoOh yeah, bait and switch. If Google abused an API and went against the terms would you complain about bait and switch when the access was disabled?
- pjscott 14y agoSo, suppose that (a) companies start sending useful metadata with their emails, (b) other clients like Outlook add support, and then (c) GMail capriciously removes support. As long as the metadata keeps getting sent, and there are clients which can do interesting things with it, I don't see the problem here.
- v13inc 14y agoAs a vendor, the registration would be extremely annoying. Since these widgets are meant to replace HTML links and buttons, I would then have to create and support 2 versions: the fancy widget version all the providers I registered with, and a fallback for providers that don't support it.