4 ms·

> Makers of Twitter clients were eventually reminded of this fact in a rather painful way. Isn't this a risk with all federated protocols - private or public i

• obviouslygreen 13y ago
  I would say not exactly: If you have a public protocol and it's intended to run in multiple places or in a distributed manner, then even if the rest of the world stops using it, you and your users can happily chug along in your own sandbox. If it's only used or useful in the context of a privately-owned/controlled environment... then you're in trouble, or likely to get there..
  • davewiner 13y ago
    That's absolutely correct. Google Reader ignored an important part of the RSS 2.0 spec, but I kept producing content that they couldn't parse, and if people used the tools that existed before GR, they didn't notice any difference, even though GR came to dominate RSS aggregators. BTW, that's probably a reason why Twitter never could really support RSS, not because the spec didn't cover what they were doing, rather Google didn't.
• austenallred 13y ago
  I would say yes, but unfortunately most of those that took that gamble have been shut out. If Twitter were really smart about the whole thing, given the amount of money they have, they should let others develop off of their platforms and acquire them as they start to gain traction.
  • davewiner 13y ago
    Instead, Twitter stays frozen in time. There haven't been any new features for users in years. Lots of features for advertisers.