documentation help requested for new mediawiki

[PaulKroll]

Has there been any consideration of replicating the Wikipedia architecture, that is, having a squid cache in front of the Mediawiki pages? Mediawiki, directly accessed, is a CPU-drinking, database-beating dog. A powerful one, to be sure, but with anything resembling traffic, it'll bring a normal server to its knees.

[Richard Berg]

I'll worry about that when the time comes.

[partystar]

As for as I know MediaWiki has basic search functionality for all page content. However, uploaded files are not indexed.As shown by Wikipedia, MediaWiki is capable of handling very high traffic. There is no automated navigation within MediaWiki. Pages can be placed tagged with categories, which allow them to be listed on special category pages.There is a navigation box but editing it requires editing a configuration file on the file system and some other configuration.

[Fizick]

Richard Berg,
please kill spam robot at mediawiki

[Richard Berg]

I have implemented all of the spam suggestions from this page (http://wiki.evernex.com/index.php?title=Blocking_Spam_in_Mediawiki):
- block edits that try to hide spam in DIV tags
- block blank user agents
- block phony/suspicious user agents, referrers, and other HTTP patterns (bad-behavior (http://www.homelandstupidity.us/software/bad-behavior/))
- require CAPTCHA when registering new users and when adding new external links, except for sysops
- installed a blacklist of domains. It pulls the list from Wikimedia, plus sysops can add additional spam domains to this page (http://avisynth.org/mediawiki/Spam_Blacklist).

Anonymous users can edit pages again without registering. I'm optimistic these defenses will make registration unnecessary.

[gzarkadas]

I just edited the spam list as normal user and removed a blocked link, then succesfully entered a spam link in another page (see the wiki logs). As it is now the list can be easily tampered by a spammer.

[Fizick]

Richard, thanks for protection!

Can you set some new category of "trusted" (human) users to work without CAPTCHA?

I am not sure that anonymous edit is good.

Anyway, we need help for new mediawiki!

[Richard Berg]

I just edited the spam list as normal user and removed a blocked link, then succesfully entered a spam link in another page (see the wiki logs). As it is now the list can be easily tampered by a spammer.
Thanks for reminding me. It should be restricted to only sysops now.

In the past we got many valuable fixes from anonymous users. People do not like registering for random sites (me included). The anti-spam page linked above indicated their wiki gets no bot spam even with anonymous users allowed. I think the recent flood -- where every edit came from a different users -- showed that registration is not a good spam blocker at all.

Can you set some new category of "trusted" (human) users to work without CAPTCHA?
Right now that group is sysops, which I believe is just Wilbert & me. It should not be bothersome because most edits do not have external links.

[Fizick]

The previous registration fault was absent of e-mail confirmation.

[stickboy]

Hey, sorry I haven't been that active recently. I looked at the new mediawiki version of avisynth.org recently, and it certainly looks nice, but links to the old wiki pages are broken, because all the new stuff is under avisynth.org/mediawiki.

Would it be possible to redirect links to avisynth.org/index.php?foo to avisynth.org/oldwiki/index.php?foo ? Breaking links seems kind of bad.

[Richard Berg]

There's a redirect in place for URLs without "index.php" in them, e.g. http://avisynth.org/YourFirstScript

I'll see about adding another redirect when I return from vacation.

[Fizick]

We still need in help from users, in particular to detect and remove spam (from robots).

Procedure:
1. Check Wiki recent changes at
http://avisynth.org/mediawiki/Special:Recentchanges

2. check suspicious "contributions" (usually anonymous ip) by click on (diff)

3. If it is a spam, click on "undo" after current revison text at right top of screen.

4. agree with (undoing) changes by clicking on "Save page" at the bottom of text.


Of course you are also invited to make some other useful contributions to wiki, but as a other separate posting.

[Fizick]

Richard Berg,
please add CAPTCHA for not-registered user (at last for first post from this IP)

[Richard Berg]

CAPTCHA is turned on for all users now.

edit: except sysops.

[Fizick]

Richard Berg,
can you disable captcha for more wide group of real human users (include Fizick :))

[Adub]

Is the wiki down?
I can't access it. Keep getting 503 errors.

[Fizick]

Can anybody post to wiki?

I have got


Error 403

We're sorry, but we could not fulfill your request for /mediawiki/index.php?title=Troubleshooting&action=submit on this server.

Your Internet Protocol address is listed on a blacklist of addresses involved in malicious or illegal activity. See the listing below for more details on specific blacklists and removal procedures.
....

[Fizick]

Can anybody confirm?
Try edit any page and preview results.

seems, RichardB is busy with VSS2005 update ...

[niiyan]

@Fizick
I haven't had my account in avisynth.org yet.
So I tried to create it to confirm the error.
But the same 403 error as Fizick's occurred.
I couldn't create my account.

[Fizick]

Thanks for report.
So, it is general problem with wiki. :(
All users should update to Bad Behavior 2.0.11 immediately to prevent being blocked from your own site.

http://www.bad-behavior.ioerror.us/2007/12/06/bad-behavior-2011/
On other side, spammers can not post too :)

[Richard Berg]

It should work now. Sorry about the delay :)

[Fizick]

Domain Name:AVISYNTH.ORG
Created On:05-Jul-2002 12:25:47 UTC
Last Updated On:06-Jul-2007 01:24:24 UTC
Expiration Date:05-Jul-2008 12:31:19 UTC

Registrant Name:Richard Berg

[mikeytown2]

Added more info to Levels_and_Chroma section in External_filters.
http://avisynth.org/mediawiki/External_filters#Levels_and_Chroma

Let me know if I missed any useful ones.

[Fizick]

Domain Name:AVISYNTH.ORG
Created On:05-Jul-2002 12:25:47 UTC
Last Updated On:06-Jul-2008 01:21:56 UTC
Expiration Date:05-Jul-2009 12:31:19 UTC

Thanks, Richard!

[Gavino]

What is the policy about making changes to the wiki?
Is there a page that explains how to do it?

Occasionally I see things that I think could be improved, from simple typos to incomplete examples or even factual errors, but I don't want to step on anyone's toes by just jumping in and changing things. Or would it not let me do that anyway?
Do changes get approved by someone? What stops someone putting total rubbish in?

Forgive me if these are ignorant questions - I've never used a wiki-type environment before.

[mikeytown2]

@Gavino
Just start making changes! The magic of a wiki is the community will edit it. There is a captcha that prevents most spam, and user entered junk is rare. I would recommend making a username on the wiki so when someone visits the recent changes page (http://avisynth.org/mediawiki/Special:Recentchanges), they can associate a name to the edits instead of a "random" IP.

Read this as well
http://avisynth.org/mediawiki/Avisynth:Community_Portal#How_can_I_contribute_to_the_AviSynth_documentation_project.3F

I find wikipeda helpful for learning how to edit the wiki. Also clicking edit and looking at the pages is helpful as well
http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page

[nikolai]

The entire mediawiki seems to be gone. I'm getting 404s for every page. I could swear I was looking at some of the pages just a few days ago.

On this page:
http://avisynth.org/warpenterprises/

There are links near the top for "fizick's filter stickboy's filter tsp's filter vcmohan's filter tritical's filter"
The 3 middle ones all have avisynth.org URLs and they are all returning 404 now too.

[Leak]

Ummm... looks like just about everything on avisynth.org is gone - what happened?

(avisynth.org returns a generated index page listing svnindex.css and svnindex.xsl, which are the default stylesheets used by Subversion - so I'd guess the web server setup got jumbled...)

np: Tocotronic - Du Und Deine Welt (Es Ist Egal, Aber)

[Fizick]

May be hosting is expired ? (three years since january 6, 2006 - first post at this topic)

With tracert IP is same as
http://apache2-cabo.seltzer.dreamhost.com/

[Wilbert]

It's working again! Will make a backup tomorrow.

[McCauley]

Added:
Stab (http://avisynth.org/mediawiki/Stab), YAHR (http://avisynth.org/mediawiki/YAHR), GrainFactory3 (http://avisynth.org/mediawiki/GrainFactory3), MinBlur (http://avisynth.org/mediawiki/MinBlur), DePan (http://avisynth.org/mediawiki/External_filters#Stabilization), Lanczosplusv3 (http://avisynth.org/mediawiki/External_filters#Resizers), Super Slow Sharpen (http://avisynth.org/mediawiki/External_filters#Sharpeners), new Debanding section (http://avisynth.org/mediawiki/External_filters#Debanding), AnimeIVTC (http://avisynth.org/mediawiki/External_filters#IVTC_.26_Decimation), Toon (http://avisynth.org/mediawiki/Toon), DeHalo_alpha (http://avisynth.org/mediawiki/DeHalo_alpha), vmtoon (http://avisynth.org/mediawiki/VmToon), dfttest (http://avisynth.org/mediawiki/External_filters#Spatio-Temporal_Denoisers), DeGrainMedian (http://avisynth.org/mediawiki/External_filters#Spatio-Temporal_Denoisers), MVDegrain (http://avisynth.org/mediawiki/External_filters#Temporal_Denoisers), SharpAAMCmod (http://avisynth.org/mediawiki/External_filters#Anti-aliasing), GPUBilateral (http://avisynth.org/mediawiki/External_filters#Spatial_Denoisers), new Duplicate Frame Detectors section (http://avisynth.org/mediawiki/External_filters#Duplicate_Frame_Detectors), HybridFupp (http://avisynth.org/mediawiki/External_filters#Multipurpose_Filters), NTSC tools (http://avisynth.org/mediawiki/External_filters#Multipurpose_Filters) and GradFunkMirror (http://avisynth.org/mediawiki/External_filters#Debanding)
Feel free to edit these pages, they are not complete, potentially contain mistakes, but somebody has to start with something.

Regards
McCauley

[birdinred]

marked first.
i feel benifit from the VirtualDub and Avisynth script power and the people who are bihind both.so i decide to do something i can to feedback.here's a good chance to dive deeper and communicate into each other.

i need and i can do some "english2chinese" language transfer job about the doc and wiki,and how to do and when to start,will follow the porject leader as a teamer with proudness,before it ,i will read this subject to understand what's going on.

[jmac698]

To do serious documentation, I don't recommend editing online. Instead you can use these instructions:
Tested on Windows XP3
-Get http://www.wampserver.com/en/
-Install it
-Get http://www.mediawiki.org/
-Unzip to c:\wamp\www\mediawiki (mediwiki is a new directory)
-Ensure all files are moved from mediawiki-1.17\ to c:\wamp\www\mediawiki (this is just for convenience)
-Visit localhost/mediawiki
Answer the installation questions. It will be insecure, but this is for personal use. The password to mysql is root with no password. If you follow the installation, nothing else is needed. Accept all the defaults.
-Visit http://localhost/mediawiki/index.php/Main_Page
-Edit it. Add [[MyPlugin]] at the end.
-Visit http://localhost/mediawiki/index.php/Main_Page again. Click the link for MyPlugin. You can now edit it locally, and quickly. When done, copy the contents of the edit box onto the internet wiki.

[jmac698]

How can I capture syntax color-coded text from C or Avisynth script?
Like this:

function shift(clip v, float x, float y) {
v#shift an image, x>0 shifts left, y>0 shifts up
bilinearresize(last.width,last.height,x,y,last.width,last.height)
}

[jmac698]

There seems to be a way to have the wiki automatically color code if you could upgrade the mediawiki software. Who has the keys to the server?

If there is ever to be hope of a serious documentation effort on the wiki, you need good support for it. Or maybe that's just not the way to go. One dedicated volunteer could write a pdf manual.

[Wilbert]

There seems to be a way to have the wiki automatically color code if you could upgrade the mediawiki software. Who has the keys to the server?

If there is ever to be hope of a serious documentation effort on the wiki, you need good support for it.
Sorry, that's not going to happen. Richard Berg is practically unreachable. I also don't see why you need that for a serious documentation effort, although i don't disagree that it will be more readable. I ported our wiki to a pdf once, but nobody wanted to maintain that.

I personally write new articles in html or just doc and copy it to wiki when it is ready. Perhaps that's a better way to go if you write something new. Aside that i'm very grateful that you are writing something about creating c plugins!!!

[jmac698]

I generally like to prepare to do things properly, if I have time, and if I were to write a professional document, certainly color coding would make that appearance. No it's not necessary. I'd like to see the whole wiki organized properly, the info is there but it's not categorized well. If you put some thought to it, there's a difference between searching when you know what you want and browsing to discover new information that might help you. Since the wiki allows sharing, wouldn't it be possible to import the whole project to another free service?

But by all means, I and we all have to thank Richard for his generosity in providing that server.

[jmac698]

Problem solved.
http://avisynthnew.wikinet.org/wiki/Avisynth_Plugin_Development_in_C

Now with syntax highlighting. Oh yeah, also the entire wiki has been imported. Is there anything not CC I should remove? And I'm willing to give out accounts to the community, so we never lose control of it.

[Gavino]

jmac698, I appreciate you're trying to be helpful, but this seems to be using a sledgehammer to crack a nut, solving a 'problem' that no-one else cared about.

I don't wish to denigrate or discourage your efforts, but wouldn't your time have been better spent correcting the errors on that page, rather than making it look pretty?

[jmac698]

All that matters is I care :)

It doesn't matter. Call it my own wiki for personal use if you wish. I'm putting my new pages there instead.

[Wilbert]

@jmac698,

A pity that you removed your stuff from the wiki. Can I at least put it on our wiki when you have finished it?

If Richard's server runs into problem we can always move to that free server. It's this one (http://wikkii.com/wiki/Free_Wiki_Hosting) right? They seem to delete wikis though without giving people notice and doing a proper review (as you can read in the forums).

[jmac698]

It's on http://avisynthnew.wikinet.org/wiki/Avisynth_Plugin_Development_in_C
I'm using features that won't port to the avisynth wiki. You can try though, since I released CC. It's no problem really which server it's on, unless as you say it gets deleted.

There's actually a reason I won't put some of my stuff on Avisynth wiki as well; I don't agree that code should be licensed CC, it's simply not appropriate. The CC FAQ itself says so. Also the GPL FAQ says documentation should be in another license. So they both agree with each other.

I'm quite happy puttiing my stuff on this new server, I find it much easier to work with and I don't have to consult with any community over organization or format. I think I just need my own venue anyhow, there's been people tracking my forum posts across the internet in search of some restoration approach and I've never put it all together into one spot.

[Wilbert]

There's actually a reason I won't put some of my stuff on Avisynth wiki as well; I don't agree that code should be licensed CC, it's simply not appropriate.
I agree with that. Note that the SDK package is licensed under the GPL (and not CC). See http://avisynth.org/mediawiki/Filter_SDK/SDK_license.

[jmac698]

Sure, you agree, but I had feedback when posting some code and had to remove it from the wiki. I can't find the history for that right now. It might have been my measure script.

[Wilbert]

but I had feedback when posting some code and had to remove it from the wiki.
These were scripts and not code snippets in de SDK package. You removed the scripts because you wanted to license them under the GPL.

[jmac698]

I'm confused by your response, are you saying scripts are not code, but documentation? In an educational sense, code snippets are certainly part of documentation; but to me, a standalone script is a piece of code to itself. Otherwise, javascript, vbscript, even all python programs could be considering documentation.
The GPL mentioned source as, the necesary files to create or change a program, roughly speaking.
Documention can describe code; an algorithm; but can't run it.

[jmac698]

After much trouble, I managed to finish one section of the new guide ;)
http://avisynthnew.wikinet.org/wiki/Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin

[Wilbert]

I'm confused by your response, are you saying scripts are not code, but documentation?
I don't want to get into a philosofical argument whether a script can be considered to be code, or code can be considered to be documentation, since that's not relevant here for the discussion here. The main point is:

Everything which is located under http://avisynth.org/mediawiki/Filter_SDK is licensed under the GPL (as you can read it in the link i posted). So you should have moved it there instead of the original location :)

Everything which is not located under http://avisynth.org/mediawiki/Filter_SDK (so the rest of the wiki with the script snippets) is considered to be documentation and licensed under CC-SA 3.0.

I hope it's clear now ...

[jmac698]

Yes, that makes sense now! Thanks.

[vcmohan]

After I got access and editing permissions I have put on descriptions of a number of my plugins in the avi wiki. However when I tried to search for them on Google, I get my own page of plugins and no mention of the wiki page. Same is the case when I click on any of my plugins in the external filters page of Avisynth. I also find that on this external filters page, all my plugins were shown to accept RGB32, RGB24, YUY2 and YV12 color formats only while most of them accept all supported formats of 2.6 version. How do I correct this?