[linux-audio-user] the Linux soundapps pages redux

[MarC]

I know many of you don't like registration but I really think it is the 
simplest way to avoid spam and graphities.

Let's say it loudly: registration means writing once in every session 
(and when you register) your name and a password!
And now at WikiLearn, you don't need even a valid email (even if they 
ask for it...) to register.

On the other hand, I think you could continue those pages as a subtopic 
of LinuxAudio at:
http://twiki.org/cgi-bin/viewauth/Wikilearn/LA_LinuxAudio
( but ask before Randy or me, because we are not 100% about the name of 
the pages now....
maybe we will finally call it: 
http://twiki.org/cgi-bin/viewauth/Wikilearn/LinuxAudio (my wish) )

It's already hosted and works great. If you think that something should 
be changed tell us your opinions and let's build one single site 
improved by all of us.

However suggestions like "non-registration" won't be accepted so if you 
don't like TWiki, we will link your page and it will be also fine.

What do you think about it? I've already begun the "SoundCards" topic if 
you want to see how the syntax looks like...


    see at LinuxAudio


    List of topics: "Sound cards - Real-life experiences and
    annotations"
    <http://twiki.org/cgi-bin/viewauth/Wikilearn/LA_SC_SoundCards>



En/na Hans Fugal ha escrit:

>On Wed, 08 Dec 2004 21:22:42 -0500, Dave Phillips <dlphilp at bright.net> wrote:
>
>  
>
>>Do wikis present any particular problems for servers hosting them ? I
>>ask because I don't own the servers that host the soundapps sites, and I
>>certainly would not want to risk losing the good will of the providers.
>>For those of you who don't know, Matt Probst maintains the US server,
>>the folks at ATNET in Austria host the European site, and Kenji Yasaka
>>provides the Japanese mirror. They have all donated the server space,
>>bless their heads, and I want to be sure I don't screw with their security.
>>    
>>
>
>Wikis in general don't pose any problems. Depending on implementation
>there may be a slight increase in cpu cycles consumed. Instiki, the
>wiki implementation I'm using, only has one dependency: ruby. It runs
>on its own port and can run as any user at all, so security should be
>a minor issue. I'm not sure whether it will run as a module or CGI
>under apache but I can imagine some might prefer that.
>
>Like has been discussed elsewhere, you would want to have static
>mirrors everywhere but the master location where all the edits happen.
>So finding one person willing to install ruby and allow instiki to run
>is the only requirement.
>
>  
>