Main Page Discussion Page --Ted Vollers 16:19, 25 May 2011 (CDT)
Once we have some more content pages completed (I see Ted has already done quite a few), how will we let visitors know about them? I think some sort of "Table of Contents" or other type of launch pad into the content on this main page should be created. This is common on most wikis as well. Many people new to MBT might not know what to search for due to some of the unique terminology. Some recommended starting pages listed on the main page might be useful for them. --Michael Saganski 22:42, 30 May 2011 (CDT)
Displaying the contents for access.
I have done some looking around and compared to WikiPedia. It looks like the Community Portal page is where you normally set this up. This is where those categories(?) that David set up an add on for recently come in and the tree function(?) that he also added. There are ways to do this. We just don't know them yet and I have been doing other things so far. I figured once we had some content, I would start to worry about this. I have also had some problems to deal with on the board. Ted Vollers 00:32, 31 May 2011 (CDT)
- For sure Ted, I just wanted to identify the need - there is no rush yet. --Michael Saganski 08:59, 31 May 2011 (CDT)
Regarding the community portal I would think that it should using the category tree that I install we can decide how we want to categorize the content and then attach the appropriate categories to each page. From there we can insert a category tree that will help in navigation. These category trees are hierarchical in nature and can either be hierarchical fragments or can extend all the way up to a parent node. When inserting a category tree it can start anywhere in the tree, so we can get creative with this.
On the community portal page we can perhaps highlight the main pages and then perhaps use the main pages to branch off into finer details with category trees. And example of a category tree is the following
I created a category tree example for you to see on the wiki. This will give you a visual of what I am talking about. I think that everything should eventually filter up to "Home" category, but it it doesn't have to be this way. It could be that we have some trees that are not attached to "Home" (fragments I mentioned above).
I inserted a tree on the Universe Category page with <categorytree mode=pages>Universe</categorytree> (Universe can be replaces with any node in the tree)
You can click on the + sign beside Galaxy and expand out into the sub categories / pages that I created for this example. You will see a combination of subcategories and then pages branching off from the categories that they fall under,
The tag above can be use to start at any branch in the tree for any tree that exists on the site and can be placed on any page. Notice that when you are actually on one of the subcategory pages you can see where you are at the bottom of the page and click the link to navigate back up the tree until eventually you reach the top root / parent node (In this case Universe).
I think by looking at how I am doing this, it may be the best way to learn. --David Mathis 11:42, 2 June 2011 (CDT)
- I like the way this works, although it was a little confusing for a couple minutes. --Michael Saganski 13:33, 2 June 2011 (CDT)
This page seems to be getting a lot of random spam from anonymous users with different IP addresses. They are probably scripted bots that roam the internet looking for MediaWiki sites that allow anonymous posting for easy spamming. Is there something we can do about this? One fix would be to require registration for posting on discussion pages, but this would require changes to the current philosophy and approach of this Wiki.--Michael Saganski 15:55, 17 July 2011 (CDT)
I have this page on watch but there are things here that I don't remember seeing. Specifically your mention of spammers or spam bots, Mike. The thing to do is do a rollback and then go to the previous version and do a block on the identifying IP address. Or the reverse order if you prefer. I see no reason why we have to give a warning or second chance. If we have to we can eventually require registration or possibly one of those graphical discriminators to allow posting to catch bots. --Ted Vollers 07:22, 18 July 2011 (CDT)
Mike you are correct, the ability to post on talk page without registration is by design and we would like to keep it this way.
Regarding the spam, I will get the site all fixed up throughout the coming week(s). I intentionally did not place any spam filters on the wiki so that I could see with my own eyes what would happen (more of a curiosity while the wiki is still new . It's clear to me that spam prevention is needed as it can be very annoying and cause a distraction. I plan to do several things that I feel will greatly reduce and perhaps eliminate most spam. --David Mathis 07:43, 18 July 2011 (CDT)
Good to know, thanks. Yeah I've been rolling back their changes. A graphical discriminator (i.e. type the word you see in the image) is a pretty good method that I forgot about.--Michael Saganski 10:27, 20 July 2011 (CDT)
Ignore last spam, installing a spam filter. Was me. I create another page that nobody is watching for testing purposes. --David Mathis 10:49, 22 July 2011 (CDT)
All of my visitors from out of town have gone home so today I have been installing some spam prevention extensions and making some configuration changes that I feel might reduce or eliminate spam. I can't guarantee a complete elimination because there's always the possibility that a legitimate person might simply bypass all of this. To eliminate all spam would require that we disallow editing period. We all need to make an effort to watch the "Recent changes" page for spam.
What I have done:
1) Added regexp rules to block CSS Hidden Spam. 2) Added CAPTCHA QuestyCaptcha that requires that non-users answer My Big TOE related questions to edit talk pages. I feel that this alone may stop almost all spam because the person will be required to actually study MBT to post. Likely too much work for spam losers, but will shall see. 3) Installed the "Bad behavior" extension which analyzes requests for suspicious behavior, poorly faked agent strings, or connections originating from known spam addresses. 4) Installed the "SpamBlacklist" extension which blocks spam by analyzing edits to the wiki and searching for URLs that are known spamvertised sites. If it finds one, it will refuse the edit and tell the user what's wrong with the page.
Hopefully this will greatly reduce the amount of spam we have been seeing lately. :) --David Mathis 10:43, 3 August 2011 (CDT)