User talk:Xevo

.testing {font-weight: bold}

test2

Request Extension
http://www.mediawiki.org/wiki/Extension:PovWatch Sounds nice and useful, but I have no idea what wiki this is running on since Special:Version doesn't work, which either means we run a very old version. Or heavily modified and broken here and there. Rather have something like a watchlist system like a category page, where you can link stuff you want to have looked at by someone experienced, but couldn't find anything like it. Neouni 06:17, April 26, 2011 (EDT)


 * Please see my reply on your talk: "Wiki style changes applied ?". ShoeMaker 06:48, April 26, 2011 (EDT)


 * I have re-enabled Special:Version. I've always thought of it as a bit of a security risk. I managed to hide the php/mysql part in it though, so I'm ok with it now. I'll check out that extension. My first impression is the spam implications of it though ;) --Xevo 20:55, April 26, 2011 (EDT)

Un-deleting pages
I noticed you gave me some more user rights, so I decided to look and see if I could un-delete a template that may have been wrongly deleted per 's request. Even with now full user privileges, I do not see a way for me to un-delete the template or even to view the actual page that was deleted. Is this something you can tweak the user privileges so that people with Developers (Deprecated ) or maybe even System operators can do? As a side note, I've noticed that a lot of the DDO_wiki: (Developers (Deprecated ), Stewards, Bureaucrats, System Operators, Bots, DDOwiki VIPs) pages are missing or have incorrect information. If you have a few free minutes, could you populate them with just a raw list of the actually privileges each has or email me such a list. I would appreciate that. I occasionally get a request to do something that is out of the current privilege scope and would like to be able to refer people to those pages to let them know I am not just ignoring or putting them off. Thanxs ShoeMaker 09:01, March 7, 2012 (EST)

Extension Request: Labeled Section Transclusion

 * How would this extension affect the ongoing project that I started before I moved? Adding locations of scrolls, wands, and potions.  This project also included cleaning up all of the shop pages throughout the wiki and making them universal in format. Ague (Contributions &bull; Message) 20:26, April 29, 2012 (EDT)



Coding example:

On the Aulandar Thistlecrown (Vendor NPC Page): . . . Scrolls available:
 * description = Aulandar Thistlecrown is a vendor of level 3-7 divine scrolls.
 * Banishment
 * Cometfall

. ..


 * Spell Resistance
 * Word of Recall

}}

On the House of Wizardry (Shop Page): . ..

Divine Scroll Vendor - Levels 3-7
Aulandar Thistlecrown

Kind of a rough example, but as you can see, the vendor NPC page can list what he/she sells under 'description' in the template, flagged with this selective transcluding tags. This information will be pulled into the shops' page using this extension.

If the information is listed on both the shop page and the NPC page, it makes it hard to maintain and redundant, especially if the vendor changes what he/she sells in future updates. This extension would allow for one change and automatic synchronization across any transcluded pages, by simply modifying the NPC page. Plus, we can hone in on just the info we want to include with the tags. Taurolyon (Contributions • Message) 21:54, April 29, 2012 (EDT)


 * Easiest way to automatically keep list what a shop is selling is having a Category:Sold in (or something more fitting) where every article that is sold in the shop is included. Listing what is sold in a shop is quite bad idea as it quite fast becomes a horribly long list that has little value to the reader. Rather use the category page for showing what is sold. Usually transclusion just brings more and more information to the article that is not relevant and should be cowered in its own article. BlackSmith (Contributions &bull; Message) 06:04, March 9, 2013 (EST)

Replace Patrol?
I was poking about on wikipedia and I found they use this as their anonymous edit filter. Extension:FlaggedRevs I know that you were looking at doing a core update pretty soon, and it might help us with filtering some of the deconstructive anonymous edits, before they happen. - Just something to take a look at. "Tauro" (Contributions • ) 01:41, May 8, 2012 (EDT)

Extension:Widgets and Namespace editing privileges.
When you upgraded the wiki, we both forgot about privileges for editing the Widget namespace. I went to add a Twitter feed widget, and discovered that no-one can edit the namespace... I'm thinking the best was to do it is to add the privilege to Sysop instead of creating a separate widget editor user group... At least for now... We may find that it would be safe and requested to add it to say super user at a later date, but I don't think we should start there. I'll toss you an email on the subject as well. ShoeMaker (Contributions • ) 09:13, September 14, 2012 (EDT)


 * This is fixed. Sysops now have permission to edit WIdget pages. --Xevo (Contributions &bull; Message) 20:43, September 18, 2012 (EDT)

reCAPCHA API update
How was the capcha implemented? If we're running the old form request/challenge system, we should update to the new API - https://developers.google.com/recaptcha/docs/mediawiki - I think with some fine tuning we could reduce the amount of the spambots able to signup to the wiki. "Tauro" (Contributions • ) 14:43, October 22, 2012 (EDT)


 * We are using http://www.mediawiki.org/wiki/Extension:ConfirmEdit. Maybe Re-Captcha has been broken again? Sometimes the spammers will figure out how to programmatically solve the captchas, then google will update their system. I'll look at this in more detail later tonight. --Xevo (Contributions &bull; Message) 08:36, October 23, 2012 (EDT)


 * Spammers seem to be able to circumvent the recapcha verification. I did check and it is still able to block the human user, but a scripted bot still seems to make it through.

I'm doing what I can with the blocks, checking IPs and blocking spammer subnets and hosts that only provide web services (VPS and dedicated servers), but the IPs are coming from worldwide, and include some end user DSLs, cable modems, public IPs and I even found a mobile IP in the mix. I can't block these subnets, as potential wiki users may be originating from them (most of them are too large, anyways - The wiki can only block up to a /16 CIDR). "Tauro" (Contributions • ) 02:34, October 27, 2012 (EDT)


 * It makes me wonder if re-captcha has been broken again. Also, the IPs dont seem to be in the blacklists I am using. --Xevo (Contributions &bull; Message) 14:50, October 27, 2012 (EDT)


 * To me it seems like a single group/individual is targeting this site. All of the usernames look similar. I cannot tell if they broke the captcha or if a human is really solving them. The account registrations are far enough apart that someone could just be creating accounts manually. I'm not sure what to do at this point. It's really getting out of hand. If anyone has any suggestions, please let me know. In the mean time I will continue to try to find some solution. --Xevo (Contributions &bull; Message) 11:12, October 28, 2012 (EDT)


 * I'm going to try a different captcha called Asirra. This one makes the user select all of the cat photos out of a selection of both cat and dog ones. --Xevo (Contributions &bull; Message) 11:33, October 28, 2012 (EDT)


 * Looks like they are still registering even with the new captcha. I don't think they are solving the captcha programmatically. I have to wonder what the motive is for the spammers. All outgoing links on the wiki have nofollow tags, so it won't help their SEO efforts at all. --Xevo (Contributions &bull; Message) 15:57, October 28, 2012 (EDT)

Semantic MediaWiki
This extension is not bad on to handle IF the categories and its structure is healthy. Otherwise it starts pulling and generating info that is inaccurate. Biggest problems that I see is that there are so many combinations categories and article/categories in incorrect use. E.g using category page for information that should be on a regular article, category members that should be members of that category and so on. What is the gain that is hoped to gain from SMW? BlackSmith (Contributions • Message) 14:56, March 5, 2013 (EST)


 * This is the question I was hoping to find out from some of the more active contributors to the wiki. If it seems like everyone is on board then I will install it.

Xevo (Contributions • Message) 07:53, March 7, 2013 (EST)


 * I see that it is now installed on our sister wiki. I'd like to play with it a little there, and encourage our other administrators to do so as well, before we jump into it here.  I won't have any time to look at it much until the beginning of next week, but I'll get back to you here and send you an email as well.

Edit: This is going to be a big change for the wiki, so I felt it prudent to place a T:Poi on the talk pages of the following administrators: •  •  •  • ‎ •  •  •  •  •  • ‎ •  • ShoeMaker (Contributions • ) 08:09, March 7, 2013 (EST)



uh, so this thing is something like DPL and NCL? what exactly can we achieve with this extension? for example are these possible? things like these come in mind immediately, but probably some more example would help discussing pros and cons. yoko5000 (Contributions • Message) 11:37, March 7, 2013 (EST)
 * Automation on Adpack articles' XP/favor listing
 * Automation on spell pages' # of spells per level/school
 * Tidying up Item: section's category structure, using auto-queried categories, and solve some of the cat-bleeding too?
 * Maybe it can help us do some data-mining using graph/chart stuff?

I haven't had a chance to play with the sisterwiki's implementation, as my login and subsequent password resets don't appear to be accepted. From what I read, this could be a step to having these large pools of data stored in a database table and simply have the wiki cull this data upon demand, and populate a nicely formatted wikipage (something I've been longing for since I started wiki-editing).
 * It looks like a potent extension. It would open up some tertiary extensions especially something like Data Import would be helpful when working with large pools of data (like our DDO information project).

"Tauro" (Contributions • ) 15:08, March 7, 2013 (EST)


 * Not a single clue whats being talk about, and what am I suppose to be looking for on the torwiki?

Bladedge (Contributions • Message) 18:08, March 7, 2013 (EST)


 * Likewise, I don't really speak technobabble (or is that Tech13nobabble? *g*) so... yeah, taking myself out of the vote...

LrdSlvrhnd (Contributions • Message) 20:31, March 7, 2013 (EST)


 * From what I understand after reading the above Semantic MediaWiki link, this extension would be able to generate tables (among other things, I assume) from a database of the info on the wiki. I imagine that things like the individual monster pages, item pages, enhancement pages, feat pages, etc would be in the database and you could then use the extension to output whatever pieces of that data you choose into table and list form. If that is the case, this extension would be a big improvement over NiceCategoryList. If Semantic MediaWiki can be used to generate the tables on pages such as Mm export and Category:The Red Fens epic items, it would save us an enormous amount of time whenever Turbine decides to change half the items in the game or add a bunch of monsters to the monster manual. Instead of having to update the same information on 6 different pages, you'd only have to update the item or monster page. I am sure there are many other handy things you could do with such an extension, but for that reason alone I would be happy to get it.

Susalona (Contributions • Message) 13:00, March 8, 2013 (EST)



I can only speak to what I'm familiar with, but I see a lot of duplication across the website as it pertains to listing item properties. Some items have their properties manually displayed out on 10+ pages, this means if a property for that item gets added or removed, every page would manually need to get updated. I think it would be a good idea to move away from manually listing details where a single point of reference can be found ( a la item page ). I suggested storing item properties as variables a while back to work towards fixing the duplication, but was told that direction was not feasible without the semantic extension. Moving towards storing variables such as what I described would go a long way towards automating the display of information and cascading changes automatically when /if any changes ever happen. -Joe Joenuts (Contributions • Message) 14:26, March 8, 2013 (EST)


 * That is why I wanted this extension in the first place Joe. I just want to make sure all of our top contributors take some time to experiment with how it works on our sister wiki first.  It would suck if we put this in and no-one could use it.  I'm sure there will be a learning curve, but I would like to play with it there first to take the edge off of it if you know what I mean.

ShoeMaker (Contributions • ) 14:57, March 8, 2013 (EST)


 * SMW allows you to generate pages automatically from the already present content based on the relations between articles. e.g. If we would have C:Weapons and C:Holy bursting and you ask SMW "What weapons have the holy bursting ability?" it would conjure a page that has all those articles that belong to both of those categories. Its next step from DPL and NCL. You can make questions to it, it generates searches based on the structure and conjures relatively good results to what the user was searching. I use the term "relatively" as the SMW makes the connections based on category structure and names. The present category & page structure would not be able to return correct results as its for most part, shortly put, wrong. The SMW has hard time to understand combination categories that has become quite popular in this wiki. e.g. C:Unique item enchantments is combination of three categories. Besides it got incorrect members.

. To me, this looks like terribly same kind of solution as the Item: namespace is/was. Instead of fixing the underlying problem, there is presented a solution that is a workaround. Sure, SMW would give nice free searches for the users and maker relations and in that way server the reader better, but it also escalates the structure problem. If you have two healthy and eight sick categories and unleash the SMW, that theoretically generates all the possible combinations that can be made between articles and categories, you end up having even more corrupted ones. My professional opinion is that there are more sick than healthy categories nowdays in the wiki. BlackSmith (Contributions • Message) 17:33, March 8, 2013 (EST)


 * k.....can someone show me an example on the torwiki. Not 100% sure what Iam looking for. So far iam leaning to a yes.

Bladedge (Contributions • Message) 17:56, March 8, 2013 (EST)


 * Simple example from torwiki (and only that I could find in 10mins), a tutorial to what SMW is and a better example. You are looking the third type of pages that handle only meta data. Articles cower all the things that fit to their topic name while categories collect all the articles & categories that correspond to fitting category name. What SMW adds is Property: that is a additional dimension to a wiki that tells what is the relation between the previous two. If you don't tell the relations, the SMW is crippled.

BlackSmith (Contributions • Message) 05:15, March 9, 2013 (EST)



I think you may be confusing the semantic extension with the multi-category search extension http://www.mediawiki.org/wiki/Extension:Multi-Category_Search. My understanding of semantic is that you can create additional attributes ( properties ) to be stored and then later retrieved *FROM OTHER PAGES*.

So for example, on the madstone boots page you could define a set of item modifications ( dex +4, striding 20%, etc ), and then from another page like reavers fate loot you could retrieve that set of modifications dynamically. So should the modifications ever change, increase, decrease, all references are propogated automatically when the original page defining the modifications is updated.

I've requested an account on torwiki, I'll try to figure out more details about syntax / implementation, give some better examples of functionality once account is created. Joenuts (Contributions • Message) 09:25, March 9, 2013 (EST)

IRC
Hey, if you're not too busy, see me on real quick... :) ShoeMaker (Contributions • ) 09:55, March 19, 2013 (EDT)

Been a while.
elliottcable speaking. There's apparently no e-mail address associated with my account, so I can't recover my password (which is faintly ridiculous …).

Let me know what you need to verify my identity. ;)
 * Email me, we'll figure it out. Ken doesn't pop in very often. ShoeMaker (Contributions • Message) 11:09, June 7, 2013 (EDT)


 * holy crap, it's elliott! :)

I reset the email to the Elliottcable account to your ell.io address. Xevo (Contributions • &uArr; top &uArr;) 21:41, June 7, 2013 (EDT)

dpl test
I'm currently experimenting with dpl. Things are now at a point where I think you personally should have a look at it. I'd like to attract your attention to User talk:Aldyron/Sandbox/Category Waist items experiment. Aldyron (Contributions • Message) 13:25, September 10, 2013 (EDT)

Could it really be?
I see an edit from you editing your common.css... Is it really you though? You're still around? There's a lot of stuff that could use your attention, and if you've got the free time, I think you, myself, and some of the other active editors should try to catch up on IRC or Google or something and see what we can get done. ShoeMaker (Contributions • Message) 19:44, May 10, 2014 (EDT)


 * Hey, yea I'm always *around*, I just don't really post anything ;) Currently I'm seeing if I can get a mobile skin working. Xevo (Contributions • &uArr; top &uArr;) 20:10, May 10, 2014 (EDT)

Hop on IRC with us
Hey Xevo, hop on IRC with us... It'll be easier to coordinate getting everything working right. :) Semi-protected pages are currently not editable and preference pages return internal errors for example. So much easier to do this in real time on IRC though. :) ShoeMaker (Contribs • Message<span class="emailLink emailTechnical_13"> • Email ) 20:04, October 26, 2015 (EDT)

SphinxSearch
Good show. Had SphinxSearch stopped working? &rArr; PurpleSerpent (Contribs • Message • Email ) 08:37, March 15, 2022 (EDT)
 * I switched over to just use the default search for now. I will revisit changing search extension that we use when I upgrade the wiki the newest LTS version -- &rArr; Xevo (Contribs • &uArr; top &uArr; • Email ) 09:10, March 15, 2022 (EDT)


 * The current default Wiki search is terribly restrictive (that's putting it politely). So hopefully, you'll be able to install something both more functional and flexible fairly soon. Having SphinxSearch, was probably one of the most useful features of the wiki from my own personal perspective.

&rArr; Dywypi (Contribs • Message • Email ) 11:47, March 15, 2022 (EDT)


 * Aye. SphinxSearch looks like it's fairly outdated at this point, but do make sure to look out for a search tool that can do "within text" searches - having to match the title still isn't the most helpful method. &rArr; PurpleSerpent (Contribs • Message • Email ) 12:36, March 15, 2022 (EDT)


 * This is the search that we were using: CirrusSearch. I do agree that is it better than the default search. It just wasn't worth trying to fix while being on an outdated mediawiki version. I will start working on the upgrade to 1.35 this weekend. -- &rArr; Xevo (Contribs • &uArr; top &uArr; • Email ) 13:03, March 15, 2022 (EDT)