Content added Content deleted

Inline

Revision as of 04:28, 7 March 2012

Archived sections

Put new stuff below here

Attack page?

Template:Unimpl Page/Not implemented and Category:Programming Tasks were both recently, uh, 'vandalized' by User:Umobytuz who linked them to http://osobageqys.co.cc and http://evicijum.co.cc which seem to be attack/exploit pages. You may wish to check on the IP address of this contributor and/or check for other similar recent additions.

I removed both links.

CRGreathouse 06:38, 24 November 2010 (UTC)

Thanks for the clear-up and notice. I took a look then blocked the user immediately. If I was too harsh, then I'd rather SC unblock than leave the guy easy access. --Paddy3118 07:09, 24 November 2010 (UTC)

No, blocking isn't too harsh. That means it's probably past time to apply active protections on templates and transcluded pages, too. --Michael Mol 14:43, 24 November 2010 (UTC)

User:ShariPantoja‎ appears to be another spammer (using their talk page). –Donal Fellows 11:43, 25 November 2010 (UTC)

Did some WP financial research

I just spent a little time digging through the Wikimedia Foundation's site, trying to find some info on how to get money from them. What results I got I put here --> Rosetta Code:Village Pump/Income#Dear Wikimedia Foundation <-- in case you missed it on the "recent activity" thing.

Not much helpful info, but I tried. Possibly you've already seen everything I found anyway. Shrug. -- Erik Siers 07:23, 3 March 2011 (UTC)

...and now something else you might ponder: Rosetta Code:Village Pump/Income#Paid Memberships. -- Erik Siers 16:00, 3 March 2011 (UTC)

RC used in a talk by Larry Wall (of Perl)

... And reviewed+blogged by me --> User_talk:TimToady#On "That Goes Without Saying (or Does It)".

Squid configuration

It looks like Squid's maximum request size is causing problems for AutoGeSHi. —Underscore (Talk)

Spammer

User:Debonairlazines6974 is a spammer (check their contributions). Alas. –Donal Fellows 12:08, 12 May 2011 (UTC)

Got it covered now. Thanks Donal. --Mwn3d 13:06, 12 May 2011 (UTC)

I've made a right mess

Mike. I made a mistake with a rename, and I tried to fix it, but the fixes keep digging me deeper and deeper into a hole. Can you back out my changes from 19:29 to 19:48 today (11th July). Cheers. Markhobley 19:53, 11 July 2011 (UTC)

Not automagically, it looks like. The 'undo' and 'rollback' features look a little more complicated for page moves that page-local edits. At work right now, and will be busy this evening. I'd suggest popping into (and hanging out in) the IRC channel and enlist some assistance and coordination there. --Michael Mol 19:56, 11 July 2011 (UTC)

Book Mention

In "A Byte of Python". --Paddy3118 12:21, 17 July 2011 (UTC)

Cool. :) --Michael Mol 12:25, 17 July 2011 (UTC)

More financial suggestions

...this time not from me, but posting here in case you missed it:

-- Erik Siers 12:46, 4 October 2011 (UTC)

Saw it then. Just been generally busy, and coping with a hardware failure. Slowly resolving these things...--Michael Mol 23:25, 14 December 2011 (UTC)

Spam users

I happened to look at the user creation log, and holy crap look at all the apparently-created-to-spam usernames -- things like "4Hjyo29LKb", "Gzs6na7KyZ", "4LwiEd2p", etc. Looks to be on the order of 5-10 spam accounts to 1 legit account.

I was thinking, there has to be a way to catch those, before they start posting their links. The only method that comes to mind is blocking their entire subnet, at least temporarily, say 30 days. That way, they can't just come back and create a new username and continue spamming, or just spam without logging in.

Might be harsh, especially if they're spamming from a normal ISP account, but maybe a short-term solution. Would likely reduce the amount of admin work, methinks. -- Erik Siers 20:20, 4 October 2011 (UTC)

They do get their source IPs blocked, and the IPs are disallowed from creating new users. I don't have a mechanism that allows me to block entire subnets, but that will become necessary when the site moves over to dual-stack IPv4/IPv6. --Michael Mol 20:32, 4 October 2011 (UTC)

And before anyone suggests it, I'm not interested in applying pattern-matching or bayesian tests on usernames. I've been caught by surprise before when an account that looked like a spam username started making beneficial edits. --Michael Mol 20:32, 4 October 2011 (UTC)

What about one of those tests that simply sends an alert to an admin? Make it a one-time thing, something like: "SpamWatchBot has noted an edit from suspicious user name apparent-spammer-name on page So-and-so. This is the only alert that will be generated for this user."

Then the bot (or whatever) could add apparent-spammer-name to an internal ignore list, and let the admins worry about it.

Eh... Looking at it now, maybe not worth the time to write. Shrug. Or maybe there's already a MW bot available to do something similar and could be modified appropriately; I haven't looked. Shrug again. -- Erik Siers 07:15, 7 October 2011 (UTC)

Right now, I see almost every edit on the wiki, as I've got the Recent Changes feed pulled in via Google Reader. Anyone who does that can see when accounts are created or blocked, and when pages are edited or moved. Frequently, someone else gets in and repairs things before I have a chance to respond. I wind up blocking the offending account, possibly deleting any 'created' pages if the person who caught the edits first didn't have delete privileges. --Michael Mol 12:52, 7 October 2011 (UTC)

It might be worth considering doing more automated banning. I've been watching the war you've been fighting over the past month or so (and flagging problem pages as I see them) and I'm wondering if it's sustainable in its current form. Is it possible to change the rules to make things harder for the scum? The logs I can see don't let me find out whether there's some common feature of the hosts submitting spam, but I bet it'll prove to be a relatively small group that's targeting RC… –Donal Fellows 17:45, 4 February 2012 (UTC)

Thanks for the flaggings. I've been thinking of taking a page from Panopticlick and [mod_security http://modsecurity.org/] and use request fingerprinting to block automated attackers. The risk of false positives is very low compared to IP-banning, and automated attack scripts are highly likely--at least for the short term--to not change their fingerprints much between attacks. --Michael Mol 17:53, 4 February 2012 (UTC)

Heads up: User:Healthytact23164, User:Gmalestripperx look very suspicious, but haven't spammed yet. –Donal Fellows

When I see new users in the recent changes feed, I add them to my watchlist. That way, I get an email when their page is created, so I can catch spam users in under five minutes, if I'm awake. --Michael Mol 17:00, 10 February 2012 (UTC)

Uploading problem

I've been trying to upload a file and the interface won't let me. It's a png file which I've cunningly disguised with a .png extension, but when I attempt to upload it I just get

Permitted file types: png, gif, jpeg, svg.

Any ideas?

I had written an elegant solution to a task but I daren't post it without its output since I get harassed whenever I have the temerity to post a solution without giving its results.

CRGreathouse 07:15, 23 November 2011 (UTC)

This is a known problem. See Image Upload problem? ~~and Problems with uploading new versions of existing images~~ on this page. -- Erik Siers 07:31, 23 November 2011 (UTC)

Ah. No solution known, then? I didn't see one at either of those links. CRGreathouse 08:22, 23 November 2011 (UTC)

The one I crossed off is probably unrelated. No response from Short Circuit so I assume no solution yet. He had a combination server move/upgrade planned; I don't know what happened with that but I guess that maybe he was hoping that the problem would disappear when he did that. If he did that. -- Erik Siers 08:27, 23 November 2011 (UTC)

There's some related discussion on my talk page, see if it's of any help. --Ledrug 08:51, 23 November 2011 (UTC)

There is a workaround linked to in the above discussion: [1]. --Mwn3d 11:57, 23 November 2011 (UTC)

I believe it to be related to "AJAX" uploads. That's what I found when I tried walking through the JS code. What I don't get is why people are still seeing that message even after I disabled AJAX uploads. Sorry for not replying directly in the other places it's cropped up; I'm beginning to think we need a real bugtracker for this stuff. --Michael Mol 14:03, 23 November 2011 (UTC)

I managed to make it work by disabling JavaScript on my browser. CRGreathouse 03:12, 28 November 2011 (UTC)

The MediaWiki software has been updated, serverside. Is this still going on? --Michael Mol 23:24, 14 December 2011 (UTC)

<math> not working?

Equations in the tasks are not being rendered for some reason. Could you check this? Thanks. --Paddy3118 07:00, 14 December 2011 (UTC)

Also broken on all other pages; for example, “<math>1</math>” here renders as

1

(which used to render as “1” because the code used to spot that it was simple enough to convert to HTML; its definitely not getting as far as trying to send the info into TeX and failing). I guess it was the weekend's server changes, and could be as simple as a missing handler for the <math> tag. –Donal Fellows 09:18, 14 December 2011 (UTC)

Should be fixed. --Michael Mol 23:23, 14 December 2011 (UTC)

Thanks Michael! --Paddy3118 04:18, 15 December 2011 (UTC)

Related Pages -- group them?

Greyscale_bars/Display, Colour_pinstripe/Display, Pinstripe/Display, and to a lesser extent Colour_bars/Display, plus their printer related tasks are all very similar. In fact, many of them center around 4 horizontal bars composed of a pattern of vertical bars, and the code is very similar between each task as a result. (Compare the AHK solutions for Colour pinstripe and Pinstripe; they differ by only a tiny bit: the few lines which distinguish between repeating colored vs repeating greyscale bars.) IMHO, they should all should be grouped together somehow, or even merged. — Crazyfirex 21:43, 15 December 2011 (UTC)

Have at it! See Template:Collection...Though that kind of thing really should be accomplished using semantic tags and inline-queries, now. Take a look at Template:Mp community. --Michael Mol 23:30, 15 December 2011 (UTC)

Hmm... how about "Graphical bars", "Graphics bars", or "Graphics patterns"? — Crazyfirex 22:07, 16 December 2011 (UTC)

More likely, something like [[task aspect::line drawing]]. At some point, we can have a box which lists the known aspects of a task, and then drill down to other tasks with the same aspect[s]. --Michael Mol 01:35, 17 December 2011 (UTC)

Most tasks actually involve filled rectangles (looking at the sources there is usually a "FillRect" and very few "DrawLine" — one uses a brush, the other a pen), so how about "rectangle drawing"?

To my mind, it's the same thing if I use a one stroke of a pen with a square brush to fill in the same set of pixels as I could with filling a rectangle. I don't have a strong feelings to care which way it goes. As the thing becomes done more properly, ambiguous scenarios like this will be wrapped up in a tree of properties and subproperties.

It does bring to mind an interesting way to draw a distinction, however: The same task, except in a rotated frame of, say, 30 degrees counterclockwise. --Michael Mol 02:07, 17 December 2011 (UTC)

Demo of IPv6 access from anon user.

SC here. Just demonstrating what an anonymous IPv6 user looks like. --2001:470:C5B9:DEAD:E269:95FF:FEC5:295F 15:24, 22 January 2012 (UTC)

Another edit, from the same user, on the same /48, but a different /64. ('beef' instead of 'dead'. This is my wifi network, as opposed to my wired network.) The final 64 bits are different, because I'm using my wireless NIC instead of my wired NIC, and the two NICs have different MAC addresses. Also, if I were dedicated to it, I could automate coming at the wiki from 2^16 different /64s. The use of IPv6 privacy extensions would allow me to randomize the MAC-derived portion, too. If it were truly necessary to block my network, you would have to do it at a /48. That should be a last resort, though. Generally, you'd block the /128 (the full, specific IP) first, followed by the /64, followed by the /56, and then the /48. The larger the subnet, the more collateral damage, so larger blocks should be last. --2001:470:C5B9:BEEF:4EED:DEFF:FE93:63A0 15:37, 22 January 2012 (UTC)

IP address to nickname change request.

Hi. Recently I discovered that I created the page Canny_edge_detector not being logged in. Is there a way to change my IP address 87.224.129.185 to my nickname `firstfire' in the history? Thanks. --Firstfire 04:28, 7 March 2012 (UTC)

Revision as of 04:27, 7 March 2012 (view source) rosettacode>Firstfire (→‎IP address to nickname change request.: new section) ← Older edit		Revision as of 04:28, 7 March 2012 (view source) rosettacode>Firstfire (→‎IP address to nickname change request.) Newer edit →
Line 146:		Line 146:
	== IP address to nickname change request. ==		== IP address to nickname change request. ==

	Hi. Recently I discovered that I created the page [http://rosettacode.org/wiki/Talk:Canny_edge_detector Canny_edge_detector] not being logged in. Is there a way to change my IP address 87.224.129.185 to my nickname `firstfire' in the history? Thanks.		Hi. Recently I discovered that I created the page [http://rosettacode.org/wiki/Talk:Canny_edge_detector Canny_edge_detector] not being logged in. Is there a way to change my IP address 87.224.129.185 to my nickname `firstfire' in the history? Thanks. --[[User:Firstfire\|Firstfire]] 04:28, 7 March 2012 (UTC)