[buddypress-trac] [BuddyPress] #4728: Visibility API refactoring/restructuring

buddypress-trac noreply at wordpress.org
Fri Dec 21 05:40:49 UTC 2012

#4728: Visibility API refactoring/restructuring
 Reporter:  chrisclayton       |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Core               |     Version:
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |

Comment (by chrisclayton):

 Replying to [comment:1 DJPaul]:
 > Where else would the existing activity visibility code be used?

 I'm currently working on a plugin (which I'm hoping to make good enough
 for a core patch) that mimic (kinda) the functionality of facebooks
 activity privacy while still having the same feel as the implementation
 used in xprofile. Eg. You'd have a drop down on the post form with
 Visibility levels, user attaches a level to the activity, the activity
 only shows to those users (this part looks like it would be dependent on
 some of Boones hide_sitewide tickets).

 I know there are a lot of people who want privacy extended to other
 components and i think its smarter if we use a generalised API, rather
 than building from scratch for individual components as many functions can
 be reused and filtered by the individual component when appropriate.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4728#comment:2>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list