1. Actionstream 0.35

    body

    I'm updating too fast.  This release brings some improvements to the UI for adding services.  There are also now options to use the plugin as a sidebar widget or with at easy-to-include post/page tag.  This release also brings the recognition of a requirement of PHP5.2.0 or higher (after much debugging with James Kirk).

    And, as always, bug fixes!

    See the plugin page for more information /download. 

    Tags:
    Creative Commons Licence © 2006-2008 Stephen Paul Weber. Some Rights Reserved.
    Stephen Weber at 2008-03-25 20:38 | 6 Comments / Trackbacks

  2. Actionstream 0.30

    body

    Some significant improvements to my ActionStream plugin. The plugin can always be downloaded from that page.  The changes are:

    1. Bugfix in how some feeds were handled (notably google reader)
    2. If nicknames are being displayed, they are hcards with links to your profile at that service
    3.  Including updates from your own blog is now optional
    4. There is now an option to remove services you have added
    5. Collapsed (5 more… et al) nodes may now be expanded on link click
    Tags:
    Creative Commons Licence © 2006-2008 Stephen Paul Weber. Some Rights Reserved.
    Stephen Weber at 2008-03-24 20:47 | No Comments / Trackbacks

  3. Actionstream Plugin Update

    body

    I am pleased to announce version 0.2 of my Wordpress Actionstream plugin!

    It can be downloaded from the normal place.

    New this release:

    1. Better microformats support in the output
    2. Some architecture improvements and bug fixes
    3. There is now a sanity check for zero items or less items than requested
    4. Posts on the host blog are now added to the actionstream
    5. There is a well defined way to add stream items (say, from another plugin). Just create an array with the fields you need (be sure to specify identifier and created_on - GUID and unix time of publish, respectively) - usually includes title and url. Then instantiate an object of class ActionStreamItem and save in like so: (new ActionStreamItem($array_data, 'service', 'data_type', $user_id))->save();
    6. There is now a hook for other plugins to add available services. Example: 
      actionstream_service_register('feed',

      array(

         'name' => 'Feed',

         'url' => '%s'

      ),

      array(

         'entries' => array(

               'html_form' => '[_1] posted <a href="[_2]" rel="bookmark" class="entry-title">[_3]</a>',

               'html_fields' => array('url', 'title'),

               'url' => '{{ident}}',

            )

      ));
    Tags:
    Creative Commons Licence © 2006-2008 Stephen Paul Weber. Some Rights Reserved.
    Stephen Weber at 2008-03-17 22:37 | 3 Comments / Trackbacks

  4. On Actionstreams and Blogging Your Own Work

    body

    So first, the plugin.  I have basically ported the MT Actionstream plugin to Wordpress (you can see it in action on my main page).  This is pretty cool, and it means we can easily share settings with other efforts.

    New in this release is the ability to import a list of services from another page (like MyBlogLog or  FriendFeed) using SGAPI.

    Code lesson: sometimes the Wordpress docs lie.  They say that you pass a function name (or array with object reference and function name) to wp-cron hooks to schedule regular actions.  Not true.  You pass the name of a Wordpress action (added with add_action).

    Blogging Lesson: Blog your own work.  This plugin has been covered by at least four blogs now (more than most of my stuff) and not yet by me.  I just posted the plugin on the DiSo mailing list and people liked it.  I'm not complaining, but I'll definately post my own stuff up front in the future!

    Tags:
    Creative Commons Licence © 2006-2008 Stephen Paul Weber. Some Rights Reserved.
    Stephen Weber at 2008-03-11 22:03 | 2 Comments / Trackbacks

  5. Content Publishing Protocol

    body

    Since APP (understand here) is mainlined in WordPress, it makes sense to use it in DiSo efforts.  I doubt that my OAuth plugin will work here, but it's worth testing.  It may mean using headers, but with comment and discovery support we should be able to build a distributed commenting system, at least for Wordpress.

    I've thought about other APIs that would be useful for DiSo.  For example, adding friends or groups.  APP does not fit this, but the general concepts do.  Perhaps APP can be abstracted into more of a CPP.

    GET on main endpoint to list items (ATOM can always be the main wrapper here).

    POST to main endpoint to create new items.

    PUT to node to edit.

    DELETE to node to delete.

    Authentication unspecified (HTTP Basic or OAuth work well).

    If the content of your POST and PUT requests is ATOM, you have AtomPub.  The same basics can easily work with other content.  (The other content types could be encapsulated in ATOM entry bodies on the GET list, or XOXO).

    For example, a POST body of XFN+hCard could add a friend.  A PUT body of hCard could edit a profile (ie, to add groups).

    I would also like to suggest that POST on a node could be used to add comments (create new content on a content node).

    Tags:
    Creative Commons Licence © 2006-2008 Stephen Paul Weber. Some Rights Reserved.
    Stephen Weber at 2008-02-20 21:45 | No Comments / Trackbacks
« Previous Posts
Next Posts »
Stephen Paul Weber