I'm quite excited about the 3rd party journal integration; particularly keen on seeing this in SunBlogNuke soon

It occurs to me though, that this still isn't 100% of the story. What would be great is to be able to use ActiveSocial as a 'comments' module for articles, videos, etc. This could be a comment thread against the journal entry for that item.

So you'd add (for example) ActiveSocial to your SunBlogNuke page. ActiveSocial is configured to look for "entryid" in the URL - if it doesn't exist, it doesn't display for the user (so as to allow comments to be linked to each blog entry).

Someone posts a blog, SBN posts to the journal - again, with the entryid.

When someone comments on the journal *or* on the blog entry, it's automatically linked to the journal entry and the blog entry, so it can be displayed on either. 

You could also *optionally* configure a setting "Does not support journal" - basically, telling AS that the module can't post to the journal, allowing you to set a content type so that when someone hits the post for the first time, it will get added to the journal; giving you a default fallback for unsupported modules.

The idea being that this gives you a unified comment system throughout the site - all it needs is to understand the tags used by a given module in the query string - while being fully integrated with the social paradigm.

Would love to also see this implemented with "thumbs up / thumbs down" ratings (ala anti-spam), both for the post and for the comment itself. Then you could implement "most popular posts" and "most popular comments", etc.

I think this idea would make for a more seamless social experience.  Sorry if this is a bit convoluted - happy to explain the idea more if needed.

Would love to also see this implemented with "thumbs up / thumbs down" ratings (ala anti-spam), both for the post and for the comment itself. Then you could implement "most popular posts" and "most popular comments", etc.

+1 for thumbs up and down feature. I use Ventrian NA. So if this is added as an API then all module vendors can add these features. Great ideas...

This has been discussed before (sorry, dont have link!) - it would be very useful attaching comments to any entity..

Damn :-( I normally try to find previous threads rather than create new ones, so apologies .. but thanks for weighing in with support :-)

It seems the cabability is there, just not documented or fine tuned yet:

http://www.activemodules.com/Commun...fault.aspx

Ah, funnily I'd seen that too and it must be the one Rodney's thinking of too. I guess I just didn't think of it because I was thinking from a 180-degree view - eg. from a 3rd party module which has a (frankly) crap comments module and no journal integration. That plus thinking about how we're achieving 3rd party module support for AS (eg. by recognising ASUID in the query string) got me thinking of how AS could make my life easier with just a little extension along the same lines.

It's a funny one because if AS supported this with the features as described (eg. including the "doesn't support journal" setting), it would make the 3rd party integration less dependent on others - since you could achieve *most* of the same functionality with this. That's probably not a bad thing since 3rd party devs might choke on the AS price just to develop integration for it ... (not to mention some of them not getting 'why' we want the integration, or being totally unresponsive, etc, etc)

Yes, that was it. I do the same thing with my old module - it can attach to any entity - check out this Wall for example (bottom of page) - http://www.pokerdiy.com/poker-chip-...lator.aspx

It takes in a custom variable (in this case TabID). I would love to see this in ActiveSocial so I can display a consistient UI to my users - every module implements comments differently.

Yeah exactly. It gives you that pervasive consistency, especially when you see all comments showing up in the journal timeline, which makes discoverability and discussion so much easier for users.