Re: [microsound] Matrix scene locations?

[macrosound@xxxxxxxxxxxxx]

No prob.  I was under the impression (still am, sort of) that there aren't
giant waves of interest in this project so I just sort of slopped
something together very informally.  I'm not quite sure how to resolve the
issue of spreading the files around.  I am running a hotline server right
now but some people have told me they couldn't connect.  You can try it..

ip: 169.254.11.71
l/p: matrix/project

if you are running a mac and you want to try and get soulseek to work I
would suggest the python version rather than the mac version.  There are
reports of people successfully running the python version on macs. 
'Soleseek', the mac version, is very very beta.  Youd have to do some net
searching for info on how to do that though.  the site for pyslsk is here:
http://www.sensi.org/~ak/pyslsk/

The only other solution is for someone to donate webspace temporarily for
this project but that usually doesn't happen.  If you really really want
the files I can send you a CD but you would have to pay for the shipping
because I am broker than broke.

good luck,
e

The pHarmanaut wrote:
> No faux pas. I definitely appreciate your taking initiative on this, don't
> get me wrong. I just thought an email had already circulated on the list
> re.
> storing these on the hotline server. I've never been able to get soulseek
> to
> run, so I was concerned about having access to the project files.
>
>> Whoa...sorry guys.  No one else seemed to be taking any initiative here
>> and I wasn't sure if it was cool to u/l to the hotline server or not.  I
>> will u/l the files directly, I agree, it makes the most sense.
>>
>> Does it really matter whether it's a noiseusse project or a microsound
>> project?  No one really looks at my site besides you guys anyway and did
>> anyone who is actually responsible for the microsound site express in
>> interest in hosting it?
>
> Sorry, my point didn't come across right. I didn't mean this in a
> proprietary sense but rather, will this, like the previous microsound
> projects, be restricted to microsound list members? If not, are you open
> to
> having the call circulated elsewhere and bringing in other stylistic
> approaches?
>
>> I'll give dev/ the concept credit, though I doubt his ego will shatter
>> if
>> he's not acknowledged by me.
>
> I wasn't meaning to indicate that devslashnull should get the credit for
> this. The collaboration arose out of a dialog between multiple
> participants,
> a fact in-and-of itself unique when compared to most of the other projects
> offered up on the list. I was more interested in the fact of this
> multiplicity of interest and enthusiasm be documented in some way, and
> devslashnull's was the first name that came to mind when I thought back to
> those emails.
>
> Again, I'm all for your initiative and the project. Very intriguing! I
> can't
> wait to get the files and get to work. Sorry if my confusion came across
> as
> a lack of appreciation and respect.
>
> Thanks,
> -=Trace
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: microsound-unsubscribe@xxxxxxxxxxxxx
> For additional commands, e-mail: microsound-help@xxxxxxxxxxxxx
> website: http://www.microsound.org
>
>

------------------------------