5 ms·

I certainly don't think open means community driven, and there are many more than two reasons companies don't publish unsupported specs. One of the biggest is

I certainly don't think open means community driven, and there are many more than two reasons companies don't publish unsupported specs. One of the biggest is that they're just not ready for 3rd party clients in any fashion. The protcol may be _very_ rapidly changing. The auth workflow might be tied to some other system. And, regardless of messaging to use at your own risk, if you publish people will get mad when you break them. Finally, it's just a lot of work to go through if it's truly unsupported.

nightpool 13y ago
If your protocol is that rapidly changing, you shouldn't be launching anything to the public, period. Especially if you're replacing an existing service with it.
- marcusf 13y ago
  Why not?
  - mattmcknight 13y ago
    Because as soon as you release the spec, people will start building stuff against. This creates resistance to changing the protocol.
- cwp 13y ago
  If it wasn't being used by the public, then the protocol wouldn't be rapidly changing. Internal use, even by a company as large as Google doesn't give enough variety of circumstance and use-case to drive the changes.