User talk:Leolaporte

From The Official TWiT Wiki
Jump to: navigation, search

Thanks Leo! We now have all the css styles from Wikipedia and we can also make infoboxes and navboxes. -- Imperator3733 18:15, 9 January 2009 (PST)

Hey Leo. I've got some experience setting up MediaWiki at my place of work. If you need a power editor, I'm your man. --Listrophy 18:55, 9 January 2009 (PST)

Hey Leo

I'm wondering if I could be granted sysop rights on the wiki. I am a sysop on 2 wikis, I have created one wiki, I have years of wiki experience. I have created a few maintenance templates and I hope to create a lot more templates and some policies that should set some ground for the wiki community. I respect whatever decision you make and I hope you make the right choices in life. --Taylor Karras 12:44, 10 January 2009 (PST)

I think having a sysop from the community is a good idea and it does seem like Taylor has the necessary experience. I myself am a regular contributor to a Linux based wiki, but definitely would not be interested in doing the whole sysop thing. I think what we really need are deletion, merging, splitting and style guidelines for the community to use and for the sysop to administer with. I believe there is already a style guide up there, but the deletion, merger and splitting guidelines should probably be discussed before we settle on something. Perhaps the first duty of the community sysop could be to create an initial set of guidelines, the community could put in its input and then the sysop could incorporate any necessary changes to the final version. --Steveh 16:59, 10 January 2009 (PST)


I just noticed that Special:Upload doesn't include a drop down box with licenses (see for an example). Are all the settings set right? -- Imperator3733 16:39, 10 January 2009 (PST)

  • Hmm. When I installed it I licensed the entire wiki CC BY-NC-SA, maybe that's why? --Leolaporte 16:52, 10 January 2009 (PST)
    • When I uploaded the icons for the Delete and Improve template I just made sure that these licenses were compatible and added a copy of the licenses to the text of the images. Perhaps that would work for you? --Steveh 12:02, 11 January 2009 (PST)
      • You don't have to add licenses - the entire page is CC licensed. See the bottom. Leo 10:07, 12 January 2009 (PST)
  • Some images have an attribution clause or are published under multiple licenses, which does require a license being added. --Steveh 10:56, 12 January 2009 (PST)
  • Its probably because Wikipedia and friends have the latest beta of MediaWiki (1.16-alpha) and this wiki isnt according to Special:Version. Kirbylover4000 14:25, 11 January 2010 (PST)

Privacy Policy and Disclaimers

I noticed that there is currently no Privacy Policy or Disclaimer created. Links to them are on the bottom of every page. I think the best thing to do would be to copy the Privacy Policy and make some minor changes so it makes sense with the wiki. Should I do this or do you have something else in mind for the wiki's Privacy Policy? --Steveh 12:02, 11 January 2009 (PST)

  • Make it so, Steve! Leo 12:05, 11 January 2009 (PST)
    • It's done. I just need to verify that the server is located in Dallas, Texas before I add what jurisdiction the court orders would be under. --Steveh 21:06, 11 January 2009 (PST)
      • Yeah the server is in Dallas, but can't we make the jurisdiction where TWiT LLC is located, Petaluma, CA? Leo 10:03, 12 January 2009 (PST)
  • Well, I'm no expert in American law. Seeing as the server is located in Texas I would imagine it's subject to Texas search and seizure law and also court orders for personal information. If American law stipulates that the court order would have to go through a California court in this case that can easily be added. --Steveh 11:03, 12 January 2009 (PST)

Powerful Extensions

Hey Leo. You're a smart guy (my attempt at flattery)... you know what the semantic web is. I bet you love the idea as much as I do. I think we, all the editors of the TWiT Wiki, would benefit from having Semantic MediaWiki installed. It's an extension to MediaWiki that, if undesirable, can be turned off by commenting a line or two in LocalSettings.php. It probably will put a bit more of a load on the server's CPU, so that's one disadvantage. If we do this right, though, this wiki will be a shining beacon of semantic-ness in a world of plain-old text. Let's do it! --listrophy 17:48, 11 January 2009 (PST)

  • Interesting. I'll look into it. Leo 10:02, 12 January 2009 (PST)

Scalable Vector Graphics

I have all svg versions of basicly every kind of twit logo you can think of in svg format. which by the way is extremely small and the size is limetless. can you please allow that type of upload?. thanks Theundecided 07:45, 12 January 2009 (PST)

  • Can IE display SVG graphics now? --Steveh 07:58, 12 January 2009 (PST)
  • Absolutely. I'll turn .svg on right now. I think it's the preferred format on Wikipedia so it must work ok. Leo 09:45, 12 January 2009 (PST)
    • Looks like there's some controversy about SVG - not merely that some older browsers can't render it, but that it can contain links to other resources elsewhere. Looks like the preferred treatment is to re-render SVG uploads as PNG. I guess we'll allow SVG for a while to see what happens. Leo 09:52, 12 January 2009 (PST)

TWiT Wiki Backups and Dumps

Based on previous server crashes, community interest and the fact that this is all available under a CC license I would like to see backups of the wiki made available. Ideally this would be done automatically by a cron script which would generate two types of backups at least weekly. This is supported and built in to the MediaWiki software. The first format is a database dump which contains a copy of the text and DB structure for the pages exactly like is done for Wikipedia. This is an XML file which should probably be gzipped before serving. Secondly (and more useful for the average home user) is a dump of the wiki into static HTML files. This functionality is provided by dumpHTML and the files it produces should be tarred and gzipped. This is how the files on are created.--BenFranske 17:48, 14 January 2009 (PST)

  • I don't blame you for being gunshy! The entire server is backed up daily and stored in a different NOC. But I think a separate backup procedure is a good idea. Does this require server access or could a sysop do it? Leo 19:00, 14 January 2009 (PST)
    • A database backup would require server access, but there's also the option of giving sysops the ability to create XML dumps, which exports all content and revisions in an XML format. This page has a little information about it. --Steveh 19:05, 14 January 2009 (PST)
      • Actually, any user can export content into an xml file using Special:Export - it's the import function that only sysops can use. The only problem is it's awfully difficult to export every page like that, since you have to list the files or categories that you want to export. As far as creating full database backups, if you go to mediawiki/maintenance, use the command php dumpBackup.php --full >File_name.xml to get a full database dump. Someone with server access should do this frequently and then put the file somewhere safe. If something happens, then you use importDump.php to import a dump (since Special:Import can't import huge dumps). -- Imperator3733 22:57, 14 January 2009 (PST)
    • As mentioned above the best is to do it from the command line of the server (via SSH) requiring more than sysop status. It's a fairly simple task to create a script to create the backup file and post it to a webserver directory. Then you regularly call it via the crontab and let people download the files for distributed backup. It would be fairly easy to have the files automatically delivered to a backup server via SFTP as well. There are lots of ways to go about it but it would be nice if the raw information were generally available providing a distributed backup as well as more long-term archival. Can you tell I'm into backup as well as sharing? --BenFranske 23:10, 14 January 2009 (PST)
  • So what you're saying Ben is that you want to make daily backups that anyone could download? Easily done. I've already installed a script that makes a backup of the DB, XML, and folders. If you want I could put that into a publicly accessible folder. Question for the mediawiki experts, though. Does that reveal anything important like passwords? Leo 23:14, 14 January 2009 (PST)
    • Yes, that's what I had in mind. With your popularity I'm sure someone would always have a fairly recent copy if something went wrong and it needed to be restored as has happened with LTS in the past. I've done a few MW installs but am by no means an expert. I think that user/password data is hashed so as to not present a problem. My understanding is that using the dumpBackup utility is precisely how Wikipedia makes their database dumps available for the public so I assume it is safe. I'll wait to hear from a more experienced MW admin though. Ideally static pages would be available as well, this functionality is provided by dumpHTML and would allow more long term archiving by not requiring a MW installation to view the data. For example this would allow the data to be distributed on CD. --BenFranske 23:21, 14 January 2009 (PST)
      • I'm pretty sure dumpBackup.php does not have any user account stuff - it's just the pages. As far as in the DBs, I don't know how the passwords are stored (wouldn't they need to be unhashed somewhere so that users can get at them if they forgot their password?). If you at least get the xml dumps out there, the worst that we would need to do is import the dumps to get the pages, recreate our user accounts, and then promote the appropriate people to be admins and 'crats. -- Imperator3733 23:28, 14 January 2009 (PST)

The Leo Report

I started a page called The Leo Report that is only writable by Sysops that will contain important information regarding the wiki. It will mostly comprise policy questions. I protected it so that you can bookmark it, check it often, and know that the info contained within will be relevant.

License Choice

see: the current license makes all content incompatible to the wikipedia, maybe you can reconsider your decision? Hoffmann 22:16, 14 January 2009 (PST)

User Pages

I would like to Talk more about the User Page problem we are having. This problem mainly lays on what I want to do with my user page. First let me start by saying I understand and know the mediawiki syntax. For the past few days I have been trying to create a few templates. Mainly the ones I am trying to create is a "Infobox" and a "Navbox". To help me in creating the templetes I used the basic outline that is provide on Wikipedia. Of course I change the values and put in my info. At first I was stop (my account block for a time) and told that I was breaking copyright of Wikipedia. I was not under their term but they would not hear this. Then I tried to explain I was just using the base mediawiki syntax layout that Wikipedia had but this was not accepted. After this I found out that pages were just going to get delete because it was a "candidate for speedy deletion" under "Personal template in global namespace, useless for everybody else".

I really just wanted to know what to do. The only thing I want to put on my page is stuff about me and links to where you can find me on the internet (ie:twitter). I did not want to do this in a plain text format but want to use the wiki template system to allow for a better looking page. I was not and do not plan to use the page as a facebook or myspace type page. It is "my" calling card and I want it to look good. I think this is just over use of power and control. I have not done anything wrong or have not done anything that mediawiki did not intended for their software to do. —Preceding unsigned comment added by Khaos (talkcontribs)

You are allowed to make your user page as beautiful as you want using templates. The problem is that you're copying templates from Wikipedia which is currently incompatible. We don't have a grudge against you, and you should be able to create your own user page using other templates as your base (just look at all of the other Wikipedia user pages), but we're just you against copying templates from Wikipedia. --Taylor Karras 16:13, 15 January 2009 (PST)
  • As the one that did the bulk of the deleting I'd just like to get the other side of the story out there, the other day User:Khaos uploaded several templates (well over a dozen) and three separate sysops (not including myself who was not a sysop at the time) came to the conclusion that most of the templates were verbatim copies or derivatives of those found on Wikipedia. Khaos was warned on his user page and several times in the IRC chat by multiple sysops (a discussion that lasted well over an hour) that the pages would most likely need to be deleted, before the bulk of the templates were marked for deletion. His user page was never marked for deletion, I simply forgot to add a noinclude tag around the delete request in one of the templates I marked. Other templates existed for the sole purpose of being used on his and only his user page, most with his first and last name in the title and his personal information already entered in the template. I had those deleted because there are no circumstances where these templates would ever be used outside of his user page. A template after all is by definition designed to be reused. These elements are better left embedded directly in the user page instead of cluttering the Template namespace. Khaos is free to create his user page however he wants. What he is not free to do is use verbatim copies or derivatives of works by Wikipeidia or any content licensed under an incompatible license and he shouldn't create templates for content which will never be reused. --Steveh 16:42, 15 January 2009 (PST)
    • Sounds like a good solution. Just don't use templates Khaos - format directly on the page. And if you do feel some templates will be of general use, make sure not to make them specific to you. Leo 14:50, 16 January 2009 (PST)


  • I think the Equipment page has received most of the outside help it can get. I think the staff is going to have to fill in the blanks for us since you all are in the studio :) Also, I started a wiring diagram of the A/V setup for the Studio. Is this something you would like to have on the Equipment page as well? Sample Pic If so, I will finish it when a couple more things are added to the page. I probably will need a more detailed list of Input/Outputs as well. I have a pretty good idea of what is going on (aux outputs etc.) but need some confirmation. Willhall 17:43, 16 January 2009 (PST)
    • There is a fair amount of interest in hearing about Leo's studio setup and it is speculated on fairly regularly in the chat room. There is some information on but it is very much out of date. One of the things I'd like to do in the near future is to interview Leo via Skype about his current setup and get this information out there. People do seem to be quite interested and assuming Leo's life is something like mine in this regard the only way the information will get updated is if there is a scheduled time to talk about it. I need to get an interview pitch into Leo's mailbox, maybe I'll make that a weekend project. --BenFranske 00:02, 17 January 2009 (PST)

Namespace aliases

A while back I proposed creating namespace aliases, and since there didn't seem to be any objections, I was wondering if you could create them. The two I'm proposing right now are TW: as an alias for The Official TWiT Wiki: and TWT: as an alias for The Official TWiT Wiki talk:. To create those aliases, you would add the following code to LocalSettings.php:

$wgNamespaceAliases = array(
        'TW' => NS_PROJECT,
        'TWT' => NS_PROJECT_TALK

This will make it so that we don't have to type as much text to get to pages like The Official TWiT Wiki:Community bulletin board (instead we could just type TW:Community bulletin board or even create a shortcut like TW:CBB). -- Imperator3733 (talk | contribs | sysop | Logs: bdpr) 10:18, 21 February 2009 (PST)

Leo You rule.

Hey leo, love your shows. When i start i cant stop!!! Anyhoo, i would just like to say you might want to upgrade MediaWiki to 1.15.1 (or, if youre feeling lucky, 1.16alpha) because this wiki is running 1.13 or something?! Dont forget while you are upgrading to add this to LocalSettings.php:

$wgReadOnly="Upgrading MediaWiki";
$wgSiteNotice="The wiki will be temporarily unavailable while we upgrade MediaWiki.";

Remove them when you are done. Oh, and have a look at the UPGRADING file in the archive you downloaded just to be safe. Also, would you like me to design skins for the wiki? I often make skins so just tell me on my talk page if you want me to and how you want it to look. Thanks!!! Kirbylover4000 19:00, 11 January 2010 (PST)

Username "Justin" banned?

Just attempted to create a user "JustinClift" in order to do some basic housekeeping.

Seems any username with "justin" in it is banned. What's up with that?

Jc 01:58, 7 February 2012 (PST)

What happened was it was on a title blacklist because it was being used by spammers to create spam pages about a year ago. I have removed that name from the list so you may create that username if you wish. Geoffsan 07:18, 7 February 2012 (PST)

Translate extension

Hello, I see that this is a multilingual wiki. Have you considered using the Translate extension, which allows to easily make your MediaWiki multilingual? It makes you save enormous amounts of time which otherwise is wasted on templates wizardry, manual synchronisation of pages and so on, scarying off most translators; and offers many other aid to efficient translation. Now it's also available in handy tarball bundles. The page explains how to get help and more information, and there is extensive documentation; asking on #mediawiki-i18n @ freenode is probably your best chance for immediate assistance if needed. Thanks, Nemo 15:22, 13 January 2013 (PST)