hello.
is there a way of disabling the displaying of the ip adress of authors and the talk function (displayed in the "recent changes" and "page history"). many users do not like that there ip adress is shown in the public ...
thanks, startx.
On Tue, 29 Mar 2005 02:25:28 +0200, startx startx@plentyfact.org wrote:
hello.
is there a way of disabling the displaying of the ip adress of authors and the talk function (displayed in the "recent changes" and "page history"). many users do not like that there ip adress is shown in the public ...
Talk function no, IP showing, just tell them to register.
On 28 Mar 2005, at 16:25, startx wrote:
many users do not like that there ip adress is shown in the public ...
I don't get it. You mean if they are in a public place, like a library, or Internet café?
Or do you mean that their IP address is logged with things they write on the Recent Changes page?
If the latter, the solution is simple: they create an account for themselves.
If the former, I'd think of some polite way of saying, "get over it," after explaining that the IP address from a DHCP server is vaguely anonymous at best, and the fixed IP address from a DNS server is a matter of public record. What's the big deal?
:::: You can't solve a problem with the same kind of thinking that created it in the first place. -- Albert Einstein :::: Jan Steinman http://www.Bytesmiths.com/Van
On Mon, 28 Mar 2005 16:38:56 -0800 Jan Steinman Jan@Bytesmiths.com wrote:
If the latter, the solution is simple: they create an account for themselves.
that is what i meant. i know it is okay i would like to change the logging of not registered users from
(diff) (hist) . . N Loop unrolling; 06:53 . . xxx.xxx.xxx.xxx (Talk)
to something like
(diff) (hist) . . N Loop unrolling; 06:53 . . not registered (Talk)
if i knew where to look in the template/code i could hack it, but i haven't find that yet. so i thought there might be an easier solution.
startx.
On Tuesday 29 March 2005 01:02 am, startx wrote:
(diff) (hist) . . N Loop unrolling; 06:53 . . xxx.xxx.xxx.xxx (Talk)
to something like
(diff) (hist) . . N Loop unrolling; 06:53 . . not registered (Talk)
if i knew where to look in the template/code i could hack it, but i haven't find that yet. so i thought there might be an easier solution.
Removing anonymity of spammers is a good thing? Did I miss something?
On Tue, 29 Mar 2005 00:40:10 -0800 Paul Johnson baloo@ursine.ca wrote:
Removing anonymity of spammers is a good thing? Did I miss something?
spammers can also register. but leave it to people to decide if they want to keep anonymity could be a nice feature. or at least only displaying the adresses to the wikiadmin.
using the ip adresses displayed in "recent changes" for attacs is as bad as spamming whitout registering.
startx.
On Tue, 29 Mar 2005 11:07:56 +0200, startx startx@plentyfact.org wrote:
On Tue, 29 Mar 2005 00:40:10 -0800 Paul Johnson baloo@ursine.ca wrote:
Removing anonymity of spammers is a good thing? Did I miss something?
spammers can also register. but leave it to people to decide if they want to keep anonymity could be a nice feature. or at least only displaying the adresses to the wikiadmin.
using the ip adresses displayed in "recent changes" for attacs is as bad as spamming whitout registering.
The last "person' to spam my wiki did register. It's actually more annoying when they do register, since I needed to dig through my apache log files to track down an ip address to block. I figure that it's useless to block a spammer by name since they'll just re-register under a different one. It would actually be nice if mediawiki would keep the ip address(es) used by 'registered' users as well. Perhaps only visible to sysops.
I'd be very surprised if an internet attacker would use a recent changes list to look for victims. In any case, taking the ability to view ip addresses away from sysops would be a bad thing, and I'd prefer it if ip addresses of registered users were also tracked so that sysops could see them.
I'm not going to debate the ethnicity I'm just going to say what can/can't be done with MediaWiki and how one could do it.
On Tue, 29 Mar 2005 09:26:04 -0500, Rick DeNatale rick.denatale@gmail.com wrote:
The last "person' to spam my wiki did register. It's actually more annoying when they do register, since I needed to dig through my apache log files to track down an ip address to block. I figure that it's useless to block a spammer by name since they'll just re-register under a different one. It would actually be nice if mediawiki would keep the ip address(es) used by 'registered' users as well. Perhaps only visible to sysops.
In LocalSettings.php: $wgPutIPinRC = true;
This will place the IP in the rc_ip field in the recentchanges table. Unfortunately, I'm not sure of how to access it from the UI.
-- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Has lots of invites.
On Tuesday 29 March 2005 01:07 am, startx wrote:
using the ip adresses displayed in "recent changes" for attacs is as bad as spamming whitout registering.
How do you figure? It's only bad for people who 1) don't know how to maintain a reasonably secure system and 2) provoke someone. And in that case, they deserve what they get.
mediawiki-l@lists.wikimedia.org