3 ms·

> iMessage, Hangouts, Messenger, Slack, and all the rest use their own proprietary interfaces. For a certain core level of functionality, there should be regul

> iMessage, Hangouts, Messenger, Slack, and all the rest use their own proprietary interfaces. For a certain core level of functionality, there should be regulations and laws in place that these apps all support a public and open protocol. They can have their own, but I should be able to use imessage to send an IM to skype on the desktop. This is no different than requiring standard signalling on the wires during the era of landlines. > I still can't even save "a spreadsheet" in one program and reliably open it in another. This becomes more difficult when a spreadsheet could be the latest version of excel v. a hobby project on github. Though I expect the vast majority of spreadsheet applications will export a csv.

JoeAltmaier 7y ago
I spent 8 years in a 'startup' trying to make collaboration into a service. Couldn't get any traction. The idea of always-on collaboration services was hard for folks. They would launch the service, have a 1-hour meeting, and kill the service. With no expectation of available clients it was hard to market APIs to talk with non-existant clients. Sigh.
jefftk 7y ago
> For a certain core level of functionality, there should be regulations and laws in place that these apps all support a public and open protocol. They can have their own, but I should be able to use imessage to send an IM to skype on the desktop. Historically, open protocols like this have had a major issue with spam. How does the Skype network verify that the iMessage IM is legitimate? What about the incoming IM from the TotallyNotAFrontForSpammers service? Email is pretty much the only fully open federated push protocol, and it is only able to handle spam via complex reputation based hacks and message inspection (which is a poor fit for IM). This is no different than requiring standard signalling on the wires during the era of landlines. With the level of spam phone calls I get these days, you may see why I'm not excited about using the phone system as a model!

JoeAltmaier 7y ago

I spent 8 years in a 'startup' trying to make collaboration into a service. Couldn't get any traction. The idea of always-on collaboration services was hard for folks. They would launch the service, have a 1-hour meeting, and kill the service. With no expectation of available clients it was hard to market APIs to talk with non-existant clients. Sigh.

jefftk 7y ago

> For a certain core level of functionality, there should be regulations and laws in place that these apps all support a public and open protocol. They can have their own, but I should be able to use imessage to send an IM to skype on the desktop. Historically, open protocols like this have had a major issue with spam. How does the Skype network verify that the iMessage IM is legitimate? What about the incoming IM from the TotallyNotAFrontForSpammers service? Email is pretty much the only fully open federated push protocol, and it is only able to handle spam via complex reputation based hacks and message inspection (which is a poor fit for IM). This is no different than requiring standard signalling on the wires during the era of landlines. With the level of spam phone calls I get these days, you may see why I'm not excited about using the phone system as a model!