[1] https://developers.google.com/gmail/schemas/registering-with...
[1] https://developers.google.com/gmail/schemas/registering-with...
> 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?
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.
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.