Added flags integration as POC
Separated views completely from base heartbeat module to have heartbeat fungate as an API instead of a utitlity module

- views module filter depending on choice of message-module
- whoisuser filter for views, making it possible to use path based uid (user/uid for example)

- views update to the access handler, taking a extra filter argument acting user/requested user
- extra default block provided to show on the user /profile page

by clearing the rules cache

Merging is fixed for views aswell. Be carefull, stay with the heartbeat_row style plugin when making your own custom views

The grouping of messages is fixed now
I found a big error in my code while storing the relations of a user. Fixed.
The public and private heartbeat have been altered due to a big change in code. A peer review indicated that refraction was needed. The sollution we came up with is a message builder as context of a state pattern. The concrete state objects are derived from a base heartbeat access object performing certain taks for all states. Little implementation of a template method pattern.
Furtheron the heartbeat stores its info about relations. (init hook used to store data to the heartbeat_relations in the global user object). This info can easily be retrieved from a heartbeat instance.

Added a handlers for filtering and showing heartbeat messages with views. You can even choose access types now to fetch related users and not so public

Todo: try to run a filtering mechanisme on the the result given by views, to merge and group duplicates and related messages together, using the ui of heartbeat

added a user-user combination action to simplify things on user end

fixed bug http://drupal.org/node/349856 with renaming all stuff and adding a fixing hook_update_6300 to fix it for all users. Please run update.php

After chat with Damz: decided to leave the t-function with variables to leave as is , as this might be one of those case where it is the only thing to do