Multiple user's
sirkitree - March 10, 2009 - 16:23
| Project: | Facebook status |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | sirkitree |
| Status: | active |
Jump to:
Description
To make this module a little more functional, it should be able to handle more than just one user. I think we can do this fairly easily by moving the settings to the hook_user() instead of one general settings form.
I'll start work on this today and submit you a patch.
#1
One thing we will have to do is to be able to retrieve the user's id from Facebook. This will make it more usable, to have a user that can just put in their username (and possibly password) and get their feed. They shouldn't actually need to know where to get it, we should do this for them. Looking at the API now to see how we can pull a userid from FB.
#2
I'd welcome that.
Originally I had pushed back from this on the theory that more complex needs would be met by other modules such as Activitystream.
However, after watching the landscape for awhile, and looking at I think the approach you suggest makes sense. Activitystream's node-based approach introduces some scaling issues that we've struggled with in some of our experiments. So that's led me to look, coincidentally, at Activity.
I'm curious how you would handle creating and placing a block for a single-user site while supporting multiple users.
Probably also should move the update process from a cache-expiration model to a cron-driven model.
#3
This requires one of the following:
1) The actual feed of the status update (you can get it from http://www.facebook.com/minifeed.php?filter=11 and clicking the "My Status" link on the right hand lower corner.)
2) An application key in order to use the REST API
3) Facebook Connect (http://drupal.org/project/fbconnect) in order to use the facebook_client()->get_loggedin_user();
For now, I propose we just inform the user for now and make this simple on our end.
#4
I've placed this module "on hold" until the status of Facebook's RSS feeds is clarified. It looks like Facebook may be preparing to kill its RSS feeds, which would be a shame, because all other methods would require each Drupal site using fbstatus to get a Facebook application developer account and/or API key.