block-list: Difference between revisions
(drafted based on conversations with Jeremy Keith and Ariel Waldman) |
No edit summary |
||
| Line 19: | Line 19: | ||
== brainstorming == | == brainstorming == | ||
* XEN | * XEN | ||
== issues == | |||
Does a block list need to represent levels of animosity? Most examples in the wild are binary: either someone is blocked or they aren't (unlike XFN or other buddy list taxonomies that allow for degrees of intimacy and clarity). | |||
== see also == | == see also == | ||
* [[social-network-portability]] | * [[social-network-portability]] | ||
* [[hcard-xfn-supporting-friends-lists]] | * [[hcard-xfn-supporting-friends-lists]] | ||
Revision as of 22:57, 27 October 2007
block list
Part of the social network portability effort.
introduction
Many social networking sites provide the user the capability to "block" or "ignore" other users of those sites, typically because those other users are stalking, trolling, harrassing, or behaving negatively in some other way.
The "block list" effort documents how current social networking sites are handling these interactions in the hopes that this research can be used for developing a portable block list that a user could privately share with other sites (probably via oauth or openid or both) so that they could block a troll on one service, and have the troll automatically blocked on other services as well.
examples
The following services have a block or ignore feature.
- Flickr ("block this user" link when viewing a user's profile)
- Twitter ("block ((username))" link when viewing a user's profile, just under their friends list)
formats
Previous attempts at block list formats:
- usenet/netnews kill files
brainstorming
- XEN
issues
Does a block list need to represent levels of animosity? Most examples in the wild are binary: either someone is blocked or they aren't (unlike XFN or other buddy list taxonomies that allow for degrees of intimacy and clarity).