To access the posts from a Twitter Stream, Facebook Page or Group, or LinkedIn Company Page, you will need an API key for those services, so you'll need to create an application for them. The API key is what's used to authenticate your site for posting to, or reading from, the streams.
Once you have those, you need to setup the Channel in the admin area and authenticate with the right user on the front end. Full documentation on creating a channel (whether for posting to or reading from) can be found below:
www.sourcecoast.com/jfbconnect/docs/post...reate-social-channel
After the channel is setup, then you add those IDs to the SocialStream module.
You
do not need to leave the SCLogin module enabled on the front-end. After you've authenticated a user and they have granted permissions to their Twitter Stream or Facebook Page, you can read or post to it all you want, without them being authenticated logged into your site.
There's definitely a few steps, but that's how it has to work. Most sites also setup authentication anyways, so it's not a huge bridge to jump over to setup the Channels.
I hope that helps explain. We're working on more detailed documentation for the social stream feature soon, as well as a better configuration area for the SCSocialStream to use a checkbox system of configured channels instead of the clunky text-input area for IDs.
If you have any questions, comments or feedback, just let us know.
Thanks,
Alex
Drawing a blank on configuring 'Social Stream'
my mistake, I read that paragraph about 20 times...
With the 6.0 release earlier this year, we added the Channels feature. For that release though, all that was available was the posting of content. With 6.1, released in early July, we added the reading of streams, and simply haven't updated the docs yet to reflect that.
