blog.bazqux.com/2013/04/open-reader-api.html

Preview meta tags from the blog.bazqux.com website.

Linked Hostnames

5

Search Engine Appearance

Google

https://blog.bazqux.com/2013/04/open-reader-api.html

Open Reader API

Just received an e-mail about Open Reader API and I must say I'm totally support this initiative.We need single open vendor neutral feed-sync API.It will greatly simplify life for future and existing feed reader and client application developers.While the best solution at the moment is to mimic existing Google Reader API (that's what Marco and Oliver suggests and that's what I'm planning to do in the next few weeks) it's probably not the best solution in the long run.Reader API is undocumented, specific to Google and contains some inefficiencies (like making separate HTTP request for each item marked read). I'm sure that few dirty hacks will be required to make BazQux behave like Google Reader from API point of view.When it comes to add new features I would like to expose them via standard open API than to invent my own one and ask all application developers to support it.And I'm happy to see that there is now a place where we all can help each other create common universal feed reader API.



Bing

Open Reader API

https://blog.bazqux.com/2013/04/open-reader-api.html

Just received an e-mail about Open Reader API and I must say I'm totally support this initiative.We need single open vendor neutral feed-sync API.It will greatly simplify life for future and existing feed reader and client application developers.While the best solution at the moment is to mimic existing Google Reader API (that's what Marco and Oliver suggests and that's what I'm planning to do in the next few weeks) it's probably not the best solution in the long run.Reader API is undocumented, specific to Google and contains some inefficiencies (like making separate HTTP request for each item marked read). I'm sure that few dirty hacks will be required to make BazQux behave like Google Reader from API point of view.When it comes to add new features I would like to expose them via standard open API than to invent my own one and ask all application developers to support it.And I'm happy to see that there is now a place where we all can help each other create common universal feed reader API.



DuckDuckGo

https://blog.bazqux.com/2013/04/open-reader-api.html

Open Reader API

Just received an e-mail about Open Reader API and I must say I'm totally support this initiative.We need single open vendor neutral feed-sync API.It will greatly simplify life for future and existing feed reader and client application developers.While the best solution at the moment is to mimic existing Google Reader API (that's what Marco and Oliver suggests and that's what I'm planning to do in the next few weeks) it's probably not the best solution in the long run.Reader API is undocumented, specific to Google and contains some inefficiencies (like making separate HTTP request for each item marked read). I'm sure that few dirty hacks will be required to make BazQux behave like Google Reader from API point of view.When it comes to add new features I would like to expose them via standard open API than to invent my own one and ask all application developers to support it.And I'm happy to see that there is now a place where we all can help each other create common universal feed reader API.

  • General Meta Tags

    10
    • title
      Open Reader API | BazQux Reader news
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • generator
      Jekyll v3.8.5
  • Open Graph Meta Tags

    6
    • og:title
      Open Reader API
    • US country flagog:locale
      en_US
    • og:description
      Just received an e-mail about Open Reader API and I must say I'm totally support this initiative.We need single open vendor neutral feed-sync API.It will greatly simplify life for future and existing feed reader and client application developers.While the best solution at the moment is to mimic existing Google Reader API (that's what Marco and Oliver suggests and that's what I'm planning to do in the next few weeks) it's probably not the best solution in the long run.Reader API is undocumented, specific to Google and contains some inefficiencies (like making separate HTTP request for each item marked read). I'm sure that few dirty hacks will be required to make BazQux behave like Google Reader from API point of view.When it comes to add new features I would like to expose them via standard open API than to invent my own one and ask all application developers to support it.And I'm happy to see that there is now a place where we all can help each other create common universal feed reader API.
    • og:url
      https://blog.bazqux.com/2013/04/open-reader-api.html
    • og:site_name
      BazQux Reader news
  • Twitter Meta Tags

    3
    • twitter:card
      summary
    • twitter:site
      @BazQuxReader
    • twitter:creator
      @Vladimir Shabanov
  • Link Tags

    3
    • alternate
      /feed
    • canonical
      https://blog.bazqux.com/2013/04/open-reader-api.html
    • stylesheet
      /assets/main.css

Links

8