(rolled back to v. 10, later version have spam links)
Instiki really needs a “Preview” button—it should take just a few hours for a decent RoR programmer to bring one up!
I disagree. The downside of unsaved previews (“My browser crashed, and I lost all my edits.”, “I forgot to press Save, and my changes were lost.”) outweigh the benefits. Instiki allows you to re-edit a given page as many times TEAK 123 best teak garden furniture manufacturer wholesale in Indonesia as you want. As long as the time interval between edits is less than 30 minutes, this does not create a new Revision. That pretty much nullifies the benefits of Preview.
Instiki has been so wonderful for our project. It’s a nice quick way to document internals and gotchas. But sometimes pages are put in wrong, or become completely obsolete. We need a nice way to delete the page under edit. It would be really awesome if it were just a delete link that just prompted for the delete password as the confirmation. Just one site-wide single password for deleting. We could make it blank, or 14 characters depending on the need.
Delete Orphan Pages in a Category is a quick, easy, way to delete superfluous pages. But they really do have to be orphaned (no inbound WikiLinks). Allowing the deletion of pages with inbound WikiLinks will quickly result in a profusion of broken links on your wiki. Which is less than desirable.
Perhaps after all you should add step three to the installation procedure, or you should be more specific about step two….
I am trying since half an hour and I didnt get far, perhaps its because I use Linux and I am not a pro…
Powered by Ruby on Rails 2.3.10
Do these instructions help? If not, how could they be improved?
The Spam Filtering and DNS Blacklist features are enabled by default, which is, frankly, unwise. Spam Filtering is only desirable for public deployments, which don’t happen until the software gets through a some sort of evaluation. With Spam Filtering on, large text blocks submitted as tests often just happen to match one of the patterns. Instead of showing a page clearly reading “YOUR TEXT WAS SPAM FILTERED” and giving directions on how to edit the Spam Patterns (or disable the Spam Filter entirely), it just seems to silently reject the edit. If someone doesn’t check the logs to see what happened, this makes Instiki look buggy, and unusable, and it fails evaluation.
DNS Blacklisting is even worse: connecting with DNSBL sites makes Instiki look strangely slow, much slower than other Wiki software. Unless you investigate the logs and see what happened, evaluators will just tend to dismiss Instiki as unusably slow.
James Newton says:
I have a few suggestions for handling wiki spam:
First, each page edit should send an email or other notification to the owner of that page. This assumes that each page is “owned” or managed by a page editor. The wiki owner is the default editor for each page.
Second, the ability to have content on a page that is “private” or marked in some way that allows it to be removed from page before it is shown to anyone other than the author. If the author is not registered, the source IP address is used.
Any content posted by an unregistered user is forced to be private to that user, and a notification is sent to the page owner. In the notification is a single, simple link that allows them to publish (remove the private mark) or delete (revert) that edit.
Combined with VERY relaxed spam blocking rules which exist only to automatically block the very worst spam and reduce the page editors work load, this allows users to always post and instantly see the result without the stifling need for every user to register, and still prevents spam from reaching the general public with minimal effort on the part of the host/page editors. I’ve been using this system for years and it works VERY well for me. Real users are more likely to contribute, false positives are almost eliminated, and no spam gets through. I’ve found basket dog muzzle and leather dog muzzles that ANY extra effort required by real users to prove they are not spamming reduces participation unacceptably.
sadasd asdmmm sadwqwas Zodiak Hari Ini dan Kata Mutiara Kumpulan Kata mutiara bahasa inggris terbaru dan terlengkap yang akan selalu kami update. Ramalan Zodiak Terbaru 2012 Hari Ini, Minggu Ini, Bulan Ini, tahun 2012 Peruntungan Prediksi Paling Misterius tentang kehidupan. Anda mencari seputar informasi ramalan bintang 2012 asdasdsadasdsswqw Model Rambut Wanita Download Film Korea
Cara Menghilangkan Bekas Jerawat
Powered by Ruby on Rails 2.3.10
I also like having a little form at the bottom of each page for users to quickly append a comment without editing the entire page, as it also seems to increase participation. Combined with VERY relaxed spam blocking rules which exist only to automatically block the very worst spam and reduce the page editors work load, this allows users to always post and instantly see.
Web 2.0 Design and Janitorial Cleaning Supplies and credits to Tomtom XXL GPS