Meza needs a public v private feature switch

[freephile]

Issue details

Some wikis are private. If fire-walled, or secured to a private LAN; if registration is closed then you don't need to worry about SPAM. Other wikis are public. A public wiki has different needs such as spam fighting compared with a private wiki. If Meza could ask/detect whether a wiki was public, it could offer an enhanced feature set designed for that environment / use case / needs. Besides SPAM, crawlers are another example. Private sites don't need to worry about crawlers while public sites will want a rich set of rules. Some public sites may NOT want to be crawled at all. In special setups where a public wiki is also a reverse proxy for the real site, the proxy site should not be crawled at all. Another special setup would be if the public site changed the look of the site to produce a regular website to viewers while offering all the convenience of a wiki to editors/owners. Such a site would want a custom robots.txt that only allows indexing of the main namespace.

[jamesmontalvo3]

I think it would be better to break this issue down into the specific changes you'd like to see happen. Something like:

• Add X, Y, and Z to Meza to fight spam
• Add A, B, and C pre-built robots.txt options, as well as the ability to customize it
• Add ability to detect if a site is publicly accessible, and default Meza's spam and robots.txt accordingly