Future wiki : deciding of the software

[khal]

Hi !

The wiki will certainly be the first to be moved to the future dedicated server.

The requirements I see are :
- the possibility to login with openID/nameID (with a plugin or native)
- the ability to manage rights/permissions from a web interface

I plan to host it under wiki.namecoin.info : what do you thing ?


Do you have suggestions ? other requirements ?

[domob]

I don't know about wiki software alternatives, but when something is decided upon and it is based on PHP, I volunteer to work on native NameID logins. (If it is not PHP, I can still do it, but it will be more work and depends on how busy I am then.) OpenID should of course work mostly out-of-the-box if it is supported by the software already.

[indolering]

The only real contender here is MediaWiki. I'm assuming I will have some admin access, so I guess I should just layout what I was planning on installing.

• Whatever Wikipedia is using for their GUI/markup helper.
• Turning on live preview.
• Bad-Behavior to block bot form submissions.
• Captcha for new user signups and multiple failed log-ins.
• Nuke to help cleanup spam that gets past 3 and 4.

With the exception of Bad Behavior, I believe all of these are included in the default MediaWiki install. Bad Behavior is very well maintained and (I believe) simply looks at the requests made not the IP addresses, so Tor users should be unaffected.

If spam starts to slip through regularly, I will look into Bayesian spam filtering using this GSoC project or by reviving one of the old WikiMedia Akismet plugins. There is also a patch to run a Captcha on all submissions with external links by users with a low number of edits.

[biolizard89]

The only real contender here is MediaWiki. I'm assuming I will have some admin access, so I guess I should just layout what I was planning on installing.

• Whatever Wikipedia is using for their GUI/markup helper.
• Turning on live preview.
• Bad-Behavior to block bot form submissions.
• Captcha for new user signups and multiple failed log-ins.
• Nuke to help cleanup spam that gets past 3 and 4.

With the exception of Bad Behavior, I believe all of these are included in the default MediaWiki install. Bad Behavior is very well maintained and (I believe) simply looks at the requests made not the IP addresses, so Tor users should be unaffected.

If spam starts to slip through regularly, I will look into Bayesian spam filtering using this GSoC project or by reviving one of the old WikiMedia Akismet plugins. There is also a patch to run a Captcha on all submissions with external links by users with a low number of edits.

+1 for allowing Tor usage.

[domob]

The only real contender here is MediaWiki. I'm assuming I will have some admin access, so I guess I should just layout what I was planning on installing.

• Whatever Wikipedia is using for their GUI/markup helper.
• Turning on live preview.
• Bad-Behavior to block bot form submissions.
• Captcha for new user signups and multiple failed log-ins.
• Nuke to help cleanup spam that gets past 3 and 4.

With the exception of Bad Behavior, I believe all of these are included in the default MediaWiki install. Bad Behavior is very well maintained and (I believe) simply looks at the requests made not the IP addresses, so Tor users should be unaffected.

If spam starts to slip through regularly, I will look into Bayesian spam filtering using this GSoC project or by reviving one of the old WikiMedia Akismet plugins. There is also a patch to run a Captcha on all submissions with external links by users with a low number of edits.

+1 for allowing Tor usage.

Me too!

[khal]

The simple trick (not allowing people to post until they manually add themselves in a specified group) I used on the forum seems to be sufficient to block spammers from posting (+ later I activated google captcha for account creation).
It would be cool if we can do the same on Mediawiki.

+1 for the Tor users (I'll check what protection is still activated there and remove IP verification if still active).

edit: IP check was already disabled, tor users should be able to come.

[khal]

The future wiki is available there :
https://wiki.namecoin.info

For now, I do not have installed a reverse proxy.

[davispuh]

https://wiki.namecoin.info/
https://forum.namecoin.info/
https://namecoin.info/

are serving invalid certificates and they should be updated, it doesn't matter if it's self-signed, but it should be valid for *.namecoin.info and not expired.

[indolering]

Okay, wiki is up and running. We have a bunch of tables to fix : (

However, to ease the pain, I got the visual editor running, it won't let us directly manipulate the table *structure* but it allows us to edit the content within it. You won't go cross-eyed trying to figure it out.

After we get the tables done, I will get a new skin working (visual-editor only works with the default skin)

Oh, and remember, the LibreOffice exports wikitext!

[phelix]

LOL, just realized for the first time the new wiki is available already.

* The start page needs to be protected (is it?)
* it's hard to see that it is a wiki
* it's hard to see that you can easily register and edit pages (can you?)
* IMHO the old main page was better structured with the lists on the side
* log in / register should go to the top imho

OK, I should get my own hands dirty, isn't that the whole point of a wiki.