| Login

Marc's Voice

building the open web one bit at a time

Responding to comments on Google lock-in strategy

1.  I’m not here to debate whether or not Atom was needed or whether it as done in the ‘right way’.  Clearly anybody who wanted to get in on speccing out Atom - could - so that was nice and open.  But I remember going to Google (around that time period) and asking them about microcontent, events, schemas, namespaces - and you know what?  They said “uh - gee - we’re not really sure about that - we’ll get back to you”.  And guess what?  Nada.  Niente.  Nothing.  They enevr got back to me.  So that says to me - they either don’t give a dam about me and the rest of us - or else I’m just sme asshole has-been who they treat like shit.  Or both.

2.  So let me say that Atom was created with the best intentions but that Google is playing it like a fine violin. They probably knew that we’d all notice these (shall I call them) tendencies regarding their strategy and that folks like me would start figuring it out and blog about it.  So they then planned out ahead of time a followup strategy - “well - it’s all just extensions to APP.”  So just to be clear - in this chess game - I don’t buy NOTHING about Google just doing extensions to Atom and the APP.  Those who believe that - I’ve got this bridge for sale that connects Manhatten to Brooklyn.

3.  Now I don’t have to tell you folks what its gonna take to make Google open.  Support something BESIDES APP. Allow us to access Base via XML-RPC. As Julian pointed out - they purposefully don’t support existing standards - like longitude and latitude and they (ooops) left out the UK.  Or as Chris points out - they don’t support the international icalendar standard.  These examples have nothing to be with being Dave Winer haters.  Its just plain old school lock-in.  Square and simple.

4. Where is support for Yahoo’s Media RSS format - which isn’t really Yahoo’s anymore.  Where are the microformats?  And here’s a crazy idea - how ’bout telling us what you’re up to.  That sure would change the situation immensely.

5. Ole Euchorn points out how important this all is - when you look at something like Google payments.  How come they can’t support PayPal.  Well we all know why - right?

So in closing ladies and gentlemenI want you to understand that this is a company who told Wall St. to shove it and got away with it.  These are kids who argue over who gets the bggest bed on their 747.  Shall I say they’re John Doerr’s darlings?  They sure act it.  They get to do what they want to do. We just don’t have to support them.

Date: Thursday, August 24th, 2006 | Time: 12:07 pm
Tags:
Add a comment

No Replies

  1. Bernhard Aug 26th 2006

    I’m curious: How does supporting XML-RPC (I guess you mean the MetaWeblog API, not the transport/encoding mechanism per se) make Google more open relative to lock-in. E.g., I don’t recognize how they extended the APP with something that MetaWeblog API already supported, so I’d assume that even if they supported it, they would extend it by the exact same mechanism in order the implement the same features.

    I think the T&C and reusing existing extensions whenever possible seem much more important to keeping everything open.

  2. Bernhard Aug 26th 2006

    I’m curious: How does supporting XML-RPC (I guess you mean the MetaWeblog API, not the transport/encoding mechanism per se) make Google more open relative to lock-in. E.g., I don’t recognize how they extended the APP with something that MetaWeblog API already supported, so I’d assume that even if they supported it, they would extend it by the exact same mechanism in order the implement the same features.

    I think the T&C and reusing existing extensions whenever possible seem much more important to keeping everything open.

  3. Bernhard Aug 26th 2006

    I’m curious: How does supporting XML-RPC (I guess you mean the MetaWeblog API, not the transport/encoding mechanism per se) make Google more open relative to lock-in. E.g., I don’t recognize how they extended the APP with something that MetaWeblog API already supported, so I’d assume that even if they supported it, they would extend it by the exact same mechanism in order the implement the same features.

    I think the T&C and reusing existing extensions whenever possible seem much more important to keeping everything open.

  4. jonny

  5. jonny

  6. jonny

  7. Good site !!!

  8. Good site !!!

  9. Good site !!!

  10. Hello, her first big cock here!

  11. Hello, her first big cock here!

  12. Hello, her first big cock here!

  13. All about ass traffic

  14. All about ass traffic

  15. All about ass traffic