Comments on: Google’s Protocol Buffers … http://dossy.org/2008/07/googles-protocol-buffers/ Everything that comes out of Dossy, from the strange to the banal. Wed, 23 May 2012 18:59:04 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Dossy http://dossy.org/2008/07/googles-protocol-buffers/comment-page-1/#comment-1100 Dossy Tue, 08 Jul 2008 20:29:30 +0000 http://dossy.org/archives/000638.html#comment-1100 David: Have you actually read the OSCAR Protocol page you linked to? Specifically: <blockquote><i>"[...] Regardless of whether you write your own library or use an existing library, you must agree to and follow the Open AIM Platform Developer Agreement and Terms of Service in order to use the AIM API. You may use this documentation of the OSCAR protocol to develop, test, and deploy your own instant messaging client and you may release that client under an open source or a proprietary license."</i></blockquote> A few things: (1) Using the OSCAR protocol for uses other than developing an instant messaging client isn't covered. Can I implement my own server? Can I use the OSCAR protocol for something completely unrelated to instant messaging? (2) I have to agree to and follow the Open AIM Platform Developer Agreement and Terms of Service? You're kidding, right? ... And yes, I agree--AOL's Bucky is the holy grail that all these Web 2.0 companies are trying to invent. AOL could go down in history as the enabler of yet another "Internet revolution" ... or, they could end up as just another botched M&A in the business history texts. Want to bet me a beer as to which way things will end up? :-) David: Have you actually read the OSCAR Protocol page you linked to? Specifically:

“[...] Regardless of whether you write your own library or use an existing library, you must agree to and follow the Open AIM Platform Developer Agreement and Terms of Service in order to use the AIM API. You may use this documentation of the OSCAR protocol to develop, test, and deploy your own instant messaging client and you may release that client under an open source or a proprietary license.”

A few things:

(1) Using the OSCAR protocol for uses other than developing an instant messaging client isn’t covered. Can I implement my own server? Can I use the OSCAR protocol for something completely unrelated to instant messaging?

(2) I have to agree to and follow the Open AIM Platform Developer Agreement and Terms of Service? You’re kidding, right?

…

And yes, I agree–AOL’s Bucky is the holy grail that all these Web 2.0 companies are trying to invent. AOL could go down in history as the enabler of yet another “Internet revolution” … or, they could end up as just another botched M&A in the business history texts. Want to bet me a beer as to which way things will end up? :-)

]]> By: David http://dossy.org/2008/07/googles-protocol-buffers/comment-page-1/#comment-1099 David Tue, 08 Jul 2008 19:21:32 +0000 http://dossy.org/archives/000638.html#comment-1099 I guess this qualifies as <a href="http://dev.aol.com/aim/oscar/">under lock and key</a>. It's more a documentation for the existing protocol then a specification for deriving a new one, but it pretty much defines how FLAP, SNACs, TLVs, etc fit together, at least in the realm of AIM. Although I agree with you. I'd love to see us open up some more of our technologies, if not as is, at least in design, so maybe some open source equivalents can be considered. *ahem* bucky *ahem* I guess this qualifies as under lock and key. It’s more a documentation for the existing protocol then a specification for deriving a new one, but it pretty much defines how FLAP, SNACs, TLVs, etc fit together, at least in the realm of AIM. Although I agree with you. I’d love to see us open up some more of our technologies, if not as is, at least in design, so maybe some open source equivalents can be considered. *ahem* bucky *ahem*

]]>