Sanction log
OpenPublic

Description

Author: Daedalus969

Description:
Currently, if a user is has an active block an "edit notice" appears above their contributions on their contrib page, notifying others of the block without having to go straight to the block log.

To this end, I think it would be useful to have a "sanction log" of sorts, to track any sanctions the user is under, and any sanctions they had been under just the way blocks are tracked.

There would be two fields. The first of course is a textbox. The sanction is simply listed here with a link to the page it was created on.

There is then a checkbox if the sanction is "indef", or, if not, the next field.. or, three, are the month, day, and year the sanction expires on. This data is used to determine if the edit notice shows up or not.

I personally think this would be useful.~~~~


Version: unspecified
Severity: enhancement

bzimport added a subscriber: wikibugs-l.
bzimport set Reference to bz23316.
bzimport created this task.Via LegacyApr 25 2010, 4:08 AM
Peachey88 added a comment.Via ConduitApr 26 2010, 2:47 AM

This would probably be more suited as a extension that could be enabled/disabled per a sites choice. As to that effect I'm re-componenting it as a Extension Request.

bzimport added a comment.Via ConduitApr 26 2010, 7:37 AM

M8R-cyc3n3 wrote:

To this end, I think it would be useful to have a
"sanction log" of sorts, to track any sanctions the
user is under, and any sanctions they had been under
just the way blocks are tracked.

what kind of "sanctions" do you have in mind? ones which
the software is or is not smart enough to enforce?

if you mean allowing the system to prevent User:X from
editing page [[Y]] outright, obviously we would need
(even expect) a log for that, and it almost surely
would accompany such a feature if/when enabled.

if you mean keeping a db table full of "fuzzy" social-
construct sanctions like "civility parole" which have
no logical interpretation, i recommend closure forthwith
"WONTFIX".

bzimport added a comment.Via ConduitApr 26 2010, 8:50 AM

Daedalus969 wrote:

I was thinking more along the lines of keeping track of sanctions on a user, such as revert sanctions, topic bans, the stuff the software can't enact upon.

bzimport added a comment.Via ConduitApr 26 2010, 8:56 AM

M8R-cyc3n3 wrote:

(In reply to comment #3)

I was thinking more along the lines of keeping track
of sanctions on a user, such as revert sanctions,
topic bans, the stuff the software can't enact upon.

For that you could always apply a post-it note which
says "kick me".

bzimport added a comment.Via ConduitApr 26 2010, 9:02 AM

Daedalus969 wrote:

Not really. One cannot edit another's edit notice, without them blanking it. A notice can further easily be removed by the noted editor. Hence the need for something they can't remove, on their contribs page.

bzimport added a comment.Via ConduitApr 26 2010, 12:45 PM

Amalthea.wikimedia wrote:

You can already build such a system similar to how editnotices on en-wiki currently work: Keep those notices in separate pages, and transclude them into [[MediaWiki:sp-contributions-footer]] if they exist.

Contributions pages are still relatively low-key so the performance impact should be acceptable, and depending on how many pages we're talking about we might even get away with keeping them in MediaWiki space.

Nemo_bis added a comment.Via ConduitSep 17 2013, 9:46 AM

(In reply to comment #0)

To this end, I think it would be useful to have a "sanction log" of sorts, to
track any sanctions the user is under, and any sanctions they had been under
just the way blocks are tracked.

It already exists: it's called talk page.

As for automatic stuff, there is the "abuse log" by the AbuseFilter, which can contain anything from invisible whitespace usage imperfections to criminal libel.

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.