" 

 == Report of Indefinitely semi-protected articles == 

 Looks like they stop at T - which doesn't seem right ;).   <>  
 :Looks fixed now.   <>  
 ::No idea why it failed last time. Perhaps related to pagination? Glad it's working now, though!    

 This account made edits to Stanford Roble Gym. It has been nominated for deletion by I. You will take into account that you may comment on this proposal if this matter concerns you, if not disregard this message. That is all.   

 == Wikistalk == 

 Apologies if this has been asked elsewhere, but are there any plans to port the Wikistalk tool to other projects (e.g. dewiki, fawikisource, enwikinews)? Regards, — ''''  
 :It needs to be rewritten as the current implementation is awful. I'm not sure when I'll get around to a rewrite.    
 :: I rewrote large parts of the code tonight. It should be less horrible now.    

 ==Server Kitties== 
 Hi MZM, for the sake of the server kitties I wonder if we could trim those WP:Edits reports a little? I've been getting server strain when running it with all ten transclusions, and I suspect that could be because the whole thing now runs to over half a mb. would it be possible to write the files with two letter abbreviations for userrights instead of 18 bytes for {{aug|1=reviewer}}? It would also save quite a few kb if we dropped the commas from the edit count and the piping from the usernames and just had . In the meantime I've trimmed it back to 6,000. Chequers  
 :It's a bit unclear to me whether you're concerned about the wikitext size or the parsed HTML size. I think the sortability is what's slowing down the page load the most (I can kill that, it doesn't really serve any purpose anyway) and the user groups can be shortened by editing Template:Abbreviated user group.    
 ::I'm afraid I don't know whether the slowness is a product of the generated wikitext size that you see when you open it for editing or the size of the file that you see displayed. Abbreviating the output from the template can chip slightly at the latter but without affecting the former. But I'm fairly confident that if you substituted the template when you ran the bot so that only ""Review"""" was stored instead of ""{{aug|1=reviewer}}"" would reduce the wikitext by thousands of bytes. Hopefully this would speed up the display. Similarly removing the piping from the username would make a difference. 
 ::A couple of other tweaks that you might consider, could you date stamp the top of the 1-1000 file, and could you not display userrights for opted out users, as someone has pointed out that comes close to identifying them. Thanks Chequers''  
 ::: These are pretty good thoughts. 
 ::: I was using a template so that end-users could change the format without me needing to intervene, but substituting each week should work well enough (assuming the page save doesn't freak out over having to do so many substitutions; I don't think it will). It maintains the benefits of using a template (end-user changes) with the benefits of substituting (reduced page size, reduced subsequent rendering times). 
 ::: The user rights for opted-out users shouldn't be happening. I thought I checked the logic on that, but perhaps that was for something else. 
 ::: I'll try to get to this when I have some free time. We really need to work on more collaborative code editing. ;-)     
 ::::Thanks, especially the collaborative coding idea. I'v