block-list-issues
Jump to navigation
Jump to search
Part of the effort to develop a block-list microformat.
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). One possibility is to allow for block-list items to be tagged to perhaps reflect a folksonomy of reasons for blocking (e.g. types of trolling), perhaps with citations to online examples of misbehaviors. - Tantek 02:28, 30 July 2009 (UTC)
- Couldn't this be an addition to XFN then, or would it be out of scope? --AlexandreSolleiro 16:36, 27 Oct 2007 (PDT)
- It's not clear, since XFN has a strictly positive/neutral scope, and the use-cases (and user interfaces) of friends lists and block lists are so very different. In particular, so far, the research on block lists shows no taxonomy at all. Just a simple list of people that are "blocked". Therefore that should perhaps be the basis of a first attempt at a microformat. - Tantek 23:06, 27 Oct 2007 (PDT)
template
Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.
Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.
<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2011-MM-DD</span>
raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>