The Official Blog of Cogmap, the Org Chart Wiki



Facebook API Posts Declining

Dear Diary,

I know it has been some time since I have written, but I have been so busy!

I recently had an idea for a Facebook Application, so as usual, after stewing on it for a month, I started coding.  As usual, I am so pleased that I acted on my instincts and now have something to show for my efforts rather than just contemplating it.  I do realize that driving adoption of Facebook Apps is hard these days and my app has some advantages and disadvantages in that regard.   I will post more details later.

What I wanted to talk about briefly is an interesting phenomenon.  I started learning about the Facebook API and rapidly discovered that most of the discussion was “pre-new-design”.  In fact, much of it was pre-throttling.  As Facebook has made their service less friendly to designers, there has been less and less discussion of how to build for the Facebook Platform.  In many ways, this creates a death spiral of application development by small developers.

The result is there is very little discussion online of how to build apps using the new design.  I wish I could figure out where I could generate a good graph looking at 2 years of blog post data.  I started with Google Trends, but all that told me was that lots of people still look for information.

3 Responses to “Facebook API Posts Declining”

  1. Steve Goodman Says:

    That’s a tough cookie – I don’t know of any tools that will take a disparate group of web sites, then graph the content over time. That would be a cool little app in and of itself though, for identifying under served Google searches.

    Take a given Google search term, and run it through Google Trends to see if the search volume is increasing. If it’s increasing, run a search on that term. Spider the results for RSS feeds, then sort and sum those RSS feeds chronologically. If the amount of content is decreasing over time, then there is an opportunity to become a thought leader in that space.

    Essentially, it would be a rudimentary way to compare information demand (searches) with supply (content). I stress rudimentary, as it treats all content as equal, and weighs blogs more heavily that wikipedia, so off the bat it’s a better suited for rapidly evolving knowledge bases.

  2. brent Says:

    If Google would let me sort results for queries by date of creation or last modification, I could probably make that work for me. Or if you could query different historical instances of the Google database, that would also work. All of these are probably less painful and more likely than the system you describe. :-)

    I like it, but it sounds like a pain in the butt!

  3. Steve Says:

    Yeah, undoubtedly a pain in the butt – maybe a good master’s thesis for someone :)

    I’m looking forward to hearing what your facebook app does.