Many thanks for the quick patch - still trying to get it work, but it is perhaps just something I did not do precisely.

Looking at activity stream SQL, I wonder if it is possible for a setting where one can choose not to create local nodes (I know some functionality will be lost) for aggregated content. It is perhaps better for a site with 100s of users, where users tend to aggregate many feeds and blogs, for example, to not store third party content, but using the activitystream tables (and not node tables) just link to external data for copyright reasons.

Think this possible?

Comments

akalsey’s picture

akalsey commented
Status: Active » Closed (works as designed)

Substantially all of the data that activity stream stores is in a node. Storing it in a different table does nothing to reduce the amount of data stored, it simply moves it from one table to a different table. To be useful at all, the content from the remote sites still needs to be stored somewhere, otherwise there's nothing to be displayed. The module will always use nodes to store its data. Nodes are Drupal's mechanism for storing content, Activity Stream items are content, therefore nodes are the right place to store this.

The intent of the module is to allow users to pull their own activities from other sites into a drupal site, building a lifestream. Presumably, the user owns their own content, even when it comes from other sites, making copyright a non-issue.

If you were to want to display only a link to the content and not the content itself, you could always use the theme layer to strip out the titles and the bodies, and only show a link. I don't think a list of links with no context would be terribly useful or interesting, however.