QUOTE(Milton Roe @ Mon 19th January 2009, 4:54am)
Interesting thoughts. If there's a way to semi-protect articles so that IPs cannot edit them, I wonder if there's not some way you can tweak the software to flag articles in a different way (I don't have a name for it) such that IP accounts cannot VIEW them? (These would be two completely different flags, so that a given article could carry one, or the other, or neither, or both).
This isn't going to affect most of WP for IP viewers, but it will block IP viewers from the "adult content" part. So what? Will the Earth end?
Now, kids can still go home and register some account and look at this stuff over their home computers. But now they're dealing with mommy and daddy's draconian software browser filters, and whatever gets through THAT, is mommy and daddy's problem.
There's another function that might be written in: a way of blocking an IP from creating nameusers, as is done now if the IP is rangeblocked, but this might be invoked even if the IP is NOT blocked. At a school's request, for instance (a simple note on the IP talk page) a flag could be set so that THAT IP cannot be used to create nameusers. And thus cannot be used to view any mature content articles which are protected from viewing by IPs.
A start.
Perhaps we could call mature-content articles which are flagged so as to be only name-user viewable, as being "semi-viewable"? Sviewable vs. sprotected? It's sort of a super-symmetry there.
Swonderful, smarvelous....
I don't know if the software supports disallowing unregistered users from viewing specific pages, but I know there's a setting which would prevent unregistered users from viewing
any pages besides the main page. It might also be able to be set on a per-namespace basis, though I doubt it can be set on a per-page basis. I don't think it would be too difficult to change the software to support this sort of thing. Actually, I believe FlaggedRevisions could, in theory, be implemented to cause this effect.
If a school really wants to prevent people from editing, signing up, or logging in, they could just use a proxy or other such that disables submitting forms on wikipedia.org or its subdomains (or just en.wikipedia.org, depending on how wide they want it). Most schools already use something like that (judging by my own experience) to disable viewing and submissions on other websites, so it would be pointless to add another method by which they could.