Need a concept of a "site-wide" Ping.FM account

Organizations often want to use Ping.FM to update their social networks in one fell swoop. To this end, I've created a pingfm_actions module which can post to pingfm under any trigger or rule (i.e. when new "news" content is created, send that over to ping.fm).

What seemed to be difficult was that the existing pingfm module is somewhat user-centric. Even pingfm_post takes an account. I got around this by "faking" an $account with a site-wide API key. (So, no matter who posts the "news item," it goes to the site-wide Ping.FM account for the organization).

What seemed to be missing was a place to store the "site-wide" API key. I could put it in my pingfm_actions module, but it seemed to me like this setting might be useful to other future modules, too. So, I put it in Ping.FM's pingfm.admin.inc settings form. I put it under the advanced section.

  // pingfm.admin.inc near line 45
  $form['advanced']['pingfm_sitewide_apikey'] = array(
    '#title' => 'Ping.FM Site-Wide Account API Key',
    '#description' => 'Some modules will want to post to an account that is tied
      at the "site-wide" level.  Enter that account\'s API key if you need it. '.
      l('Ping.FM application key', 'http://ping.fm/key', array('attributes' => array('target' => '_blank'))).'.',
    '#type' => 'textfield',
    '#default_value' => variable_get('pingfm_sitewide_apikey', ''),
  );

I'm open to some discussion about what's really the best way to implement this. I suppose another workaround is to use the user 1's credentials for site-wide stuff, but that also seemed to me less flexible. That is, user 1 might be "Bob" but we still don't want to post to "Bob's" personal Ping.FM account that's stored with his $user.