Conversation

Notices

  1. Based on what he said at the time, he felt that it was too difficult to evolve #'s component specs (mostly designed & controlled by Google) once Google decided that # and interoperability in the social space was no longer desirable (coincides with the launch of #). On top of that, his company was losing money (at one point, it was ad-supported, but users rebelled against the most lucrative ad provider, Google), and most SN users relied upon him for zero-price hosting.

    Sunday, 25-Sep-16 16:36:32 UTC from fresh.federati.net
    1. @lnxw48 @clacke ??? What does google have to do with ostatus?

      Sunday, 25-Sep-16 17:05:46 UTC from social.heldscal.la
      1. @lambadalambda @lnxw48 @clacke Google was the big advocate of oStatus that promoted use of it, until they developed their own inhouse thing for Google+

        Sunday, 25-Sep-16 18:22:21 UTC from community.highlandarrow.com
      2. @lambadalambda @lnxw48 # was partially # compatible.

        Sunday, 25-Sep-16 18:04:39 UTC from quitter.se