debugged some small issues with views submodule. But now i know for sure i wont be able to display activity so powerfull as with the built in functionality.

changed views so it works in general if messages are set single. For grouped and denied messages, the number per page still does not work. A views_query alter will have to make sure all messages are fetched from the start

Changed the menu for heartbeat as Swentel indicated: Put it all together to have less confusion when working with the module.
Changed settings for streams so it's all configured together in stead of several settings forms.

Changed autoloading of object to be more performant. Other modules classes were attempted to load by heartbeat_include which incremented the load too much.
Added a hook to rebuild or retheme messages

added some usability to the paging of streams
refactored shouts so it works on a non-ahah way with reattachments of the behaviors
Altered the count of the number of messages.
Separated the group by user to summarize nodes when a node target is added. I get the impression it would be nice to log a cid as well.

Still working on it

Added a default stream for a stream for organic group activity specific. This is also a good example on how implementations work for other or custom modules.

Refactored module so heartbeat is even more an API .
Activity Streams are introduced with options to deny messages, use filters and a lot more.
Introduction of new hooks to alter messages
Introduction of new hook methods to implement filters with callback function to actualy filter the message sets.
Altered configuration in general to be.

bugfixes will continue this week.

Added functionality to only show group stuff. It is rather too custom because of the rules conditions on node-types to include this as default. This will be available as examples in blog.menhir.be.
This is conform the example of Ekes on http://drupal.org/node/538808#comment-1972990

Cleanup the duplicates logic section

Bugfix : Users that were not logged in, got to see the access type streams private and connected access type. Fixed this with an extra property in the access type build and put access check on the blocks and page.

Fixed the duplicate user-user bug again, this time i think it is the nicest solution by setting a flag for it when the two users are action equally.
Changed the way user-user logging happens and the that's was the main reason why heartbeat provides two actions to use in rules ui. one active user versus two active users.
Changed all default rules that needed adaptation

Fixed a bug from refactoring the heartbeat activity object. Merging did not went well all of a sudden. Realy need to have a couple of simpletest to cover all this

- Fixed importation of default messages when heartbeat gets installed. no need to go to the messages page for the initial import. TODO is to fix this for all implementation of other contrbibs and submodules
- Fixed the error in the issue queue where it gave a foreach error when no message attachments were found, and even a string was given in stead of array.

Added role restriction on a per message basis. This makes it possible to display friend relations only for authenticated user or whatever role but the rest public to all ... anonymous

Fixed views integration so it works like the normal views. We have a little more easy control now for displaying and theming the views.

- Changed functionality so messages are fetched by number of records and not by timestamp.
- Added pager property to info so the messagebuilder knows more on how it should display things.
- Added a per-message  property to overrule the maximum number of messages to merge together. The
  global setting is overruled if the message specific one is set. For instance, when uploading images,
  layout-wise we want to show 5 images in the summary. But if pages are the context of activity, then i
  will only show 3 of them.
- TODO Make the pager ajax compatible and add settings for each access type

Refactored the code for access type objects. Very simple now to use them. Tests seem to have changed nothing on results, which is good

adding settings to configure the displays

Changed the logic to merge messages together when there are more users involved. UI wise a new setting is thrown in at the administer message edit and add form