Clarify module's target audience

Sub.

What you say here was partially the inspiration for building this module in the first place: There was no way to do what twitter module does with facebook (at least no way without building your own module using fb.module's api, which was cumbersome).

The problem I ran into was the fact that we're sharing with multiple sites (fb/twitter and potentially even more in the future) and both of them require some sort of user interaction using the existing method. So, it becomes a user experience question: How would it look if you were to share with both twitter/fb automatically upon submit? By default, that would give you TWO popup windows after hitting submit which is definitely a bad idea.

If someone can think of a way to integrate this into a smooth workflow (rather than showing the share buttons after submit) I'd be all for that.

As a side note: the setup for this module is so simple and lightweight because we're not doing any drupal-side authentication, like the twitter/fb modules do. Setting up twitter (with oauth, etc) is more complex than I wanted and means that with a multi-user situation (where lots of users can share) it's too cumbersome for them to all setup/authenticate accounts, etc. That's exactly what I saught to avoid here.

So, that means we're using a method that requires no drupal-side authentication for users...we're simply feeding the Drupal data to twitter/fb through querystrings in a link and leaving all authentication up to twitter/fb popups....that's what keeps setup and config simple.

All that being said, if anyone has ideas on how to streamline the userflow, please share them. This is the best I could come up with given the main goal of avoiding authentication and making setup easy.

Yeah, adding content to twitter/fb with this method requires user interaction because we don't want drupal side authentication.

I think what you say, about making the workflow more understandable, is important and I'll add some info on that once I figure the best way to present it.

There's basically 2 types of people who want to share content to fb/twitter: Site owners (always sharing to the 'site' twitter/fb acct) and 'site visitors' who don't own the site, could number in the millions, and want to use their own accounts when creating content.

This module focuses on the second set with the explicit purpose of cutting out all the difficult authentication for users to setup. They just want to post, not link their accounts to the Drupal site.

So, more docs on this is a good idea. Thanks!

Added to beta3 readme and will be added to the project homepage.

A screenshot of a site using this module would be nice, too... or maybe a link to a node on a site using this module?