Wedge

Sceptic and cynic, certainly.

The basis of the conversation is simply that if you put '(c) Forum Name' at the bottom, it sort of presumes that you're claiming copyright over *everything* on the page. Copyright law does not automatically make that assertion, as in I still own my posts by law, unless I specifically agree to something granting the forum the right to make some claim of ownership over them.

The reason this escalated how it did is because I've had a number of run-ins with that particular person where he'll ask a question to try and justify something he thinks is a good idea, I'll answer it with a brief explanation as to why it's not, he'll ignore me and do it anyway and then wonder why I don't have a positive outlook on him.

Or, as cited, he'll do only the first thing that comes to mind and doesn't want to do anything more. Like he's complained quite a bit about not being able to monetise his forum, but anything requires work on his part, he's not interested in (like talking to advertisers himself, etc, but he's the first to complain that Adsense doesn't pay him enough)

Bump for the developers who would use this.

Instead of worrying about whether it's broken or not, heh, I'm not exactly familiar with Zoomedia. What would I have to do to apply it to something?

(13 files, 22KB)

Revision: 1457
Author: arantor
Date: 13 March 2012 10:31:19
Message:
! None of the settings should contain their footnotes as part of the main language strings now, where a subtext is defined it should be its own language string (so if we change markup from dfn in the future, we do it a fraction of the times we did before), which also means we get to remove a legacy piece of code while we're at it. (ManageAttachments.php, ManageMemberOptions.php, ManageNews.php, ManagePosts.php, ManageSearchEngines.php, ManageServer.php, ManageSettings.php, Admin+ManageSettings+Search language files)
----
Modified : /trunk/Sources/ManageAttachments.php
Modified : /trunk/Sources/ManageMemberOptions.php
Modified : /trunk/Sources/ManageNews.php
Modified : /trunk/Sources/ManagePosts.php
Modified : /trunk/Sources/ManageSearchEngines.php
Modified : /trunk/Sources/ManageServer.php
Modified : /trunk/Sources/ManageSettings.php
Modified : /trunk/Themes/default/languages/Admin.english.php
Modified : /trunk/Themes/default/languages/Admin.french.php
Modified : /trunk/Themes/default/languages/ManageSettings.english.php
Modified : /trunk/Themes/default/languages/ManageSettings.french.php
Modified : /trunk/Themes/default/languages/Search.english.php
Modified : /trunk/Themes/default/languages/Search.french.php

I know I blogged about it a long time ago about the things to do with banning, and to be fair a lot of that still applies (the whole deal with whitelisting and blacklisting email addresses/domains and the things concerning blocking IP address ranges)

But it's the per user stuff that intrigues me. I speculated before about a setup whereby you could remove permissions from users based on permissions, and I suggested at the time that you could do it based on warnings, so that 10% was watched but that as you increased the warnings, you could gradually remove more permissions like avatars and so on, before getting as far as post banning.

I struggled to figure out how the interface for that might look, and of course I'm always thinking of interesting new variations that can be carried out on this, as well as integrating Annoy User.[1]

So here's what I'm thinking, allowing for the defaults and so on. The first block would be a set of sliders ranging from 0 to 100 (like the issue warning screen uses) and would be the 'warning level at which...'

* users are watched
* users' avatars are hidden
* users are post moderated
* users are prevented from posting
* users are prevented from accessing the site at all

* max % warning a single moderator can apply per day
* groups allowed to issue a warning that would ban a user from accessing the site at all
* groups allowed to issue per-user punishments

That's it for general configuration. For the user-specific stuff when you're issuing the warning...

* the warning level
* whether the warning level will drop and if so by how much per day/when it will expire (only if the user can issue per-user punishments)
* per user punishments (including when they will expire)
 - no avatar
 - no signature
 - random user annoyances[2]
 - disemvowelling[3]
 - moderation
 - no forum access
 - other to be added through hooks


This seems a bit vague to me but I can't think of anything it's missing >_>

1.	And no, I'm still not going to add IP ranges to that. I never did it when I first made Annoy User, damn sure I'm not going to add it now.
2.	Essentially those from the Annoy User mod.
3.	A subtle but effective technique: go through the user's posts and remove any extraneous vowels. Leave entities and tags intact of course, but vowels in the main content get removed. Good way of annoying users, just need to remember to do it after bbc parsing and just do it on the non HTMLified contents. I already have some code for doing this.

Which one? The one in the admin search?

Eh, it's quickly added to r1456, have at it!