3 ms·

Open platforms are nice, but open standards are nicer. So yeah, open platforms win, for a while. But they're still more part of the problem than of the solution

Open platforms are nice, but open standards are nicer. So yeah, open platforms win, for a while. But they're still more part of the problem than of the solution.

teawithcarl 14y ago
Twitter missed its chance to become just such an Imternet messaging protocol, on the order of email and HTML. APP.net is a collaboration to reverse Twitter's historical lack of backbone, choosing not to evolve into that world-class protocol. Remember, @al3x Payne (+many Twitter engineers lost that battle, and left). By the way, I agree with you below about Linus Torvalds and John Carmack not joining. I do understand and believe in where you're coming from.
- thinkingisfun 14y ago
  But the thing is, a standardized protocol is open source, in that if you have the specs, you can implement it. Not just an API to a black box, but the whole workings of that box. So either I misunderstood a lot about app.net, or you misunderstood what I mean when I ramble about protocols. App.net depends on central hosting, does it not? It's not like I don't wish them luck, but unless they go the wordpress.com route -- with self-hosting/tinkering being optional -- I'm just not interested in "yet another walled garden", even if it has a genuinely well meaning gardeners, no hidden costs, no price hikes. So I'll be outside, using RSS feeds, thinking about microformats, pouting :D
  - drharris 14y ago
    ^ this. It's not a protocol, just an API, one hosted centrally by a business who is making a lot of promises. I'd like to give DC the benefit of the doubt, but let's face it; since when has a startup founder planned to stick with a company until the bitter end. What is to prevent, say, Yahoo from buying them out and locking down the API? Nothing. What's to prevent them from jacking up prices once they do get traction? Can you be absolutely sure that they won't block you (as a developer) if you build a competitive service on top of their API? What happens when they get investments from a company building "AppPic", and you're trying to build a different photo sharing service on it? I completely agree with open protocols and standards, and if we're trying to change the world, this is the way to do it. OpenID and OpenAuth solve a true pain point in people's lives, and look how long it's taken to get even a moderate amount of traction. But it's finally happening to some extent (even if it is with corporate players like FB/Google). If you want to change the world, this is the way to do it. Walled gardens, corporate promises, and hype are not going to do it.

Open platforms are nice, but open standards are nicer. So yeah, open platforms win, for a while. But they're still more part of the problem than of the solution.

teawithcarl 14y ago

Twitter missed its chance to become just such an Imternet messaging protocol, on the order of email and HTML. APP.net is a collaboration to reverse Twitter's historical lack of backbone, choosing not to evolve into that world-class protocol. Remember, @al3x Payne (+many Twitter engineers lost that battle, and left). By the way, I agree with you below about Linus Torvalds and John Carmack not joining. I do understand and believe in where you're coming from.

thinkingisfun 14y ago
But the thing is, a standardized protocol is open source, in that if you have the specs, you can implement it. Not just an API to a black box, but the whole workings of that box. So either I misunderstood a lot about app.net, or you misunderstood what I mean when I ramble about protocols. App.net depends on central hosting, does it not? It's not like I don't wish them luck, but unless they go the wordpress.com route -- with self-hosting/tinkering being optional -- I'm just not interested in "yet another walled garden", even if it has a genuinely well meaning gardeners, no hidden costs, no price hikes. So I'll be outside, using RSS feeds, thinking about microformats, pouting :D
- drharris 14y ago
  ^ this. It's not a protocol, just an API, one hosted centrally by a business who is making a lot of promises. I'd like to give DC the benefit of the doubt, but let's face it; since when has a startup founder planned to stick with a company until the bitter end. What is to prevent, say, Yahoo from buying them out and locking down the API? Nothing. What's to prevent them from jacking up prices once they do get traction? Can you be absolutely sure that they won't block you (as a developer) if you build a competitive service on top of their API? What happens when they get investments from a company building "AppPic", and you're trying to build a different photo sharing service on it? I completely agree with open protocols and standards, and if we're trying to change the world, this is the way to do it. OpenID and OpenAuth solve a true pain point in people's lives, and look how long it's taken to get even a moderate amount of traction. But it's finally happening to some extent (even if it is with corporate players like FB/Google). If you want to change the world, this is the way to do it. Walled gardens, corporate promises, and hype are not going to do it.