Show me content I'm *not* following by default?

I think the justification is that when you first join the site, you wouldn't see anything in that listing because you wouldn't be following. However, we could change this by making suggestions on that page for what the user should follow and defaulting to "following."

Another option would be to change the toggle from being between "following/not following" to "following/all". And default to all.

Hm, that would need some change in the wording. Maybe something like a toggle between "following" and "following or not":

Show all content I'm following or not sorted by...

Wouldn't it be possible to distinguish what a user sees depending on whether he/she is registered or not?

So a non-registered user sees content he/she is *not* following by default. A registered user sees content he/she *is* following by default.

Wouldn't it be possible to distinguish what a user sees depending on whether he/she is registered or not?

We already do this. Anonymous users see a completely different homepage.

You're right, I am confusing two different things.

I think the justification is that when you first join the site, you wouldn't see anything in that listing because you wouldn't be following. However, we could change this by making suggestions on that page for what the user should follow and defaulting to "following."

+1 for this, wording seems fine to me.

I'm hesitant to complicate the issue even more, but I got a request from a user today to be able to view "both." That is, users would like a filter option to see what they are following along with what they are not following, without having to switch between different filter settings.

So a default option of "all" with two additional facets for following and not following respectively?

@webchick this is why you get paid the big bucks!

Looking at the filter it may need to be reworded

Currently it is - Show me [option 1] "all content" I'm [option 2] "following" sorted by [option 3] "last updated first".

What about - Show me or Showing [formerly option 2] "any" [formerly option 1] "content" sorted by [option 3] "last updated first".

Options for any would be followed, and un-followed (is that a word?)....ooooooh what about "recommended" that would be sexy too.
Options for content would the same as your node types but you would have to drop the all off the option name.
Options for sorting would be the same unless you wanted to throw featured in there for good measure.

What about - Show me or Showing [formerly option 2] "any" [formerly option 1] "content" sorted by [option 3] "last updated first".

+1 for Showing all content following and not following. All site activity ...

Another +1 for all being added as the default. I came across this in Commons demos.

My vote is for this aproach from non english point of view (I'm Catalan / Spanish):

e.g.
Showing [all content] that [is public] sorted by [last updated first]

Showing [1] that [2] sorted by [3]

Options for [2]:

• is public
• I'm not following
• I'm following

Thanks and regards

This will be remedied by #1969088: Changes to group browsing widget & user status updates.

I marked #1898212: Change What's Going On? Page to List Content in Subscribed Groups and Following by Default as a duplicate of this issue.

I marked #1866838: New users are confused when they arrive on 'What's going on?' for the first time as a duplicate of this issue.

@gr8britton could the behavior you describe be related to #1989472: User experience: "Following" a group doesn't make group content visible on homepage under "Show all content I'm following"?

I documented similar behavior in 3.2 where following a group did not cause group content to appear on the homepage. Only posting in a group (which silently joins you as a group member) would allow group content to appear. This is fixed in the recent dev release.

We're targeting roughly late June for a Commons 3.3 release.

gr8britton,

I haven't been able to isolate why 3.3 works when 3.2 fails. But here's a hack that will get the right group content in the activity stream in 3.2.

When a user follows a group, automatically make them a group member. Since all commons 3.2 does is make you a group member of a public group when you post, all this changes is to make following a group also make you a member ("contributor" in commons vernacular). So for my use case with public groups this worked well enough, but this may not match your use case.

So, if you can't wait until 3.3, this "works"

/**
 * Implementation of hook_flag().
 *
 */
function mymodule_flag($action, $flag, $content_id, $account) {
  if ($flag->name == 'commons_follow_group') {  
    if ($action == 'flag') { 
      // In response to flagging add user to the group
      og_group('node', $content_id, array(
        "entity type" => "user",
        "entity" => $account,
      ));
    }
    if ($action == 'unflag') {
      og_ungroup('node', $content_id, 'user', $account->uid);
    }
  }
} 

It's always harder to figure out why something works than why something doesn't!

/brent

Marking as fixed now that #1969088: Changes to group browsing widget & user status updates is fixed, and adding UX tags.