User talk:Writ Keeper

Dear Writ Keeper, Welcome to MediaWiki.org!

Yes, welcome! This site is dedicated to documenting the MediaWiki software, the software behind many wikis, including that of Wikipedia and the Wikimedia Foundation projects.
Please, take a look at the following pages. They might prove useful to you as a newcomer here:

If you have any questions, please ask me on my talk page. Once again, welcome, and I hope you quickly feel comfortable here, and find this site useful documentation of the MediaWiki software.

Thanks, and regards, Rs chen 7754 08:37, 5 February 2014 (UTC)Reply

Block

Latest comment: 5 years ago5 comments3 people in discussion

I appear to have been indefinitely blocked on the English Wikipedia in a weird indirect way due to your block of User:Glodxin2 there. I logged in as that user using the password they were posting on Wikipedia, then logged back out a few minutes later. Somehow even after I logged back into my own account (this one) I am still getting a message saying "Editing from Glodxin2 has been blocked (disabled) by Writ Keeper for the following reason(s): Abuse of talkpage". I'm not allowed to email anyone or edit my own talk page, so I have to ask you to "unblock" me (or do whatever necessary to allow me to edit again) here. IntoThinAir (talk) 20:08, 12 December 2018 (UTC)Reply

Update: It only affects me on Google Chrome, not on Safari... strange. IntoThinAir (talk) 20:12, 12 December 2018 (UTC)Reply

@IntoThinAir: Have you cleared the cache (cookies) from that browser? Tropicalkitty (talk) 20:19, 12 December 2018 (UTC)Reply

Yes, I would try clearing your cache; there are instructions on how to do so at en:Wikipedia:Bypass_your_cache#Cache_clearing_and_disabling. If it doesn't, then definitely message me again and I'll see what I can do. Also, just for the record, I would recommend against logging into accounts that have published their password like that. I totally understand the compulsion (I had to fight it myself, "just to see if the password worked"), but doing so could open you up to nasty things like autoblocks and the like. It could also dilute any CUs run on the account. Finally, although this wasn't the case here, it is possible that someone could install malicious Javascript code onto their common.js page, leaving it to run on others' computers when they log into the infected account. I don't think that's highly likely, but it's probably just not worth the risk. Writ Keeper (talk) 20:27, 12 December 2018 (UTC)Reply

@Writ Keeper: Thank you so much for the advice, I can now edit again on both browsers. I will certainly keep the "don't log into an account with a public password" advice in mind from now on. IntoThinAir (talk) 00:02, 13 December 2018 (UTC)Reply