-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Nov 15, 2007 at 01:19:58PM -0500, plutek-infinity wrote:
Date: Thu, 15
Nov 2007 09:56:01 -0800
From: Ken Restivo <ken(a)restivo.org>
What is the simplest, easiest, fastest way to get
us from "hey, let's do this" to actually making music?
I love the idea of a linux-only, by-sa instance of cchost software, but I don't have
the money pay for hosting something like that right now. I looked at the cchost docs and
it seems pretty straightforward, so I'd be willing to install and set it up if someone
wants to give me a login to a web host account somewhere. Then again, everyone on this
list is probably more than completely qualified to install and configure a GPL
PHP/MYSQL/Apache web app.
http://wiki.creativecommons.org/CcHost
Looks like the "killer web app" has already been written, and it is GPL, and
someone just needs to install it and then let's start jamming!
that "someone" might well be me -- just reviewed my server bandwidth/storage
limits, and i *think* it should be fine. anyone care to throw out a quick estimate of what
the server loads might look like? i'd prefer to stay away from lossy formats.
Awesome!
Well it looks like there might be a convergence upon FLAC/44.1k/16bit for
tracks/loops/samples. You could always limit it to ogg instead of FLAC if you get too
close to your limits, or find someone else to take over hosting it if it gets to be an
expense.
I haven't been counting, but I'd guess that about a dozen people have expressed
interest. I don't know to estimate how much material everyone would upload and how
soon. I have a whole hard disk full of unfinished loops, riffs, beats, and samples, which
I'm ready to start contributing as soon as the system is alive.
I'm not sure how to estimate how much use a Linux-only, BY-SA cchost music
collaboration site would get, but I reckon that only accurate way to find out is to push
the thing live and see what happens.
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHPL00e8HF+6xeOIcRAr38AKDdij9OAFEDlgpMBq4DyKitrDVYJACgqWKA
SpG0MSTMLFxx0gnNlFlx0iQ=
=9eBp
-----END PGP SIGNATURE-----