The emergence of cloud technologies and architectures has re-defined and re-ignited interest in subscription based Cloud Communication models. There is no doubt that introduction of cloud enables many new and exciting experiences for end users and opportunities for productivity gains for enterprises.
It seems to me, that while we will continue to hear how “the Cloud” is creating a revolution for end users and enterprises, adoption of Cloud Communications has been an evolution, not a revolution.
As enterprises and Communication Service Providers (CSPs) evolve toward cloud communications, each have different business and technical drivers that will result in a number of different deployment models based on their priorities, path and pace of introduction.
Many enterprises and CSPs have initially focused on deploying private cloud solutions as a complement to their on-premises communication and existing collaboration applications. This approach enables enterprises to gain early benefits of decentralized communication applications while maintaining a private, secure deployment.
Other enterprises and CSPs are considering the introduction of public, multi-tenant communication applications delivered as a hosted or cloud service.
Still others are interested in the benefits of hybrid communication clouds that combine on-premises, private and/or public cloud communication applications and resources.
While the concept of managed and hosted services is not new, the emergence of cloud architectures has re-defined and re-ignited interest in subscription based Cloud Communication models. Every day enterprise executives, end users and IT organizations hear how “the Cloud” is a revolution and is transforming their industry. Yet, when it comes to communication and collaboration solutions for mid-size to large enterprises, the reality is that the adoption of Cloud Communications has been an evolution, not a revolution.


First of all, it seems odd to have a post about federated Twitter without mentioning OStatus, the concrete implementation of federated Twitter that already exists and works. It implements pretty much everything about Twitter that you'd care about, except for the userbase, which seems like a given for any federated microblogging implementation given that Twitter doesn't allow or support federation themselves.
Second, these criteria are not binary. With a decently functioning network, you can have enough immediacy to expect messages within a minute or so, which means you can expect enough monotonicity to only look for new messages within the most recent minute or so of your timeline, a region that normally fits on your screen without scrolling unless you're insanely popular (and thus probably not reading every message anyway).
I probably should have mentioned OStatus, but it seems to have different goals. Does it satisfy the constraints I listed, or make them irrelevant somehow?
And you're right, the constraints have tolerances, and in the absence of multi-party conversations (or to someone catching up a few minutes later) they don't really matter at all.