ARTBASE (1)
BIO
born in 1962 in Lier, Belgium.
studied filology at Louvain, Belgium.
worked a lot in bars and restaurants before i became obsessivly addicted to producing stuff on computers.
i once won a design contest of cgi-magazine and they let me go to New York for four days, that was nice.
i think in terms of writing mostly (or programming, but those are very similar processes for me)
painting is a very different process and i'm very bad at it but i do it anyway because i like the differences it produces and i like the freshness of amateurism, i guess.
what i produce new media-wise is also very much influenced by my daily practice of webdesign and programming with its concerns of usability and the pragmatic approach it implies.
studied filology at Louvain, Belgium.
worked a lot in bars and restaurants before i became obsessivly addicted to producing stuff on computers.
i once won a design contest of cgi-magazine and they let me go to New York for four days, that was nice.
i think in terms of writing mostly (or programming, but those are very similar processes for me)
painting is a very different process and i'm very bad at it but i do it anyway because i like the differences it produces and i like the freshness of amateurism, i guess.
what i produce new media-wise is also very much influenced by my daily practice of webdesign and programming with its concerns of usability and the pragmatic approach it implies.
some novelties
including:
<http://www.vilt.net/nkdee/sisforstanzas.jsp> S is 4 stanza's
<http://www.vilt.net/nkdee/yesha.jsp> A view of Yesha and its mother
greetings,
dv @ Neue Kathedrale des erotischen Elends
http://www.vilt.net/nkdee
<http://www.vilt.net/nkdee/sisforstanzas.jsp> S is 4 stanza's
<http://www.vilt.net/nkdee/yesha.jsp> A view of Yesha and its mother
greetings,
dv @ Neue Kathedrale des erotischen Elends
http://www.vilt.net/nkdee
Re: I have a suggestion for Rhizome...
for what it's worth: i think it's a great idea, Pall & hope you guys find a
way to work it out into details. It certainly would help to get the feeling
of accomplishing sth as part of the community...
Best,
dv
> -----Oorspronkelijk bericht-----
> Van: owner-list@rhizome.org [mailto:owner-list@rhizome.org]
> Namens Pall Thayer
> Verzonden: maandag 3 april 2006 18:55
> Aan: Lauren Cornell
> CC: rhizome
> Onderwerp: Re: RHIZOME_RAW: I have a suggestion for Rhizome...
>
> Hi Lauren,
> Well, hopefully, owners of some of the work currently in the
> Artbase, linked or cloned, would contribute the code for that
> work and the code would be linked to the work (i.e. "This
> code is used in ..."). I can't decide whether it should be a
> requirement that the code belong to a piece in the Artbase or
> not. I think that would make it more relevant. And just to
> make sure no-one freaks out, I'm not by any means suggesting
> that everyone with work in the Artbase release their code. It
> would be entirely voluntary and wouldn't even have to be all
> the code. If I recall correctly, the Artbase already contains
> keyword references for most major programming and scripting
> languages. I think it would be good if code could be viewed
> online as a text file instead of having to download
> everything but that could be problematic for projects that
> contain several different files.
> Submission to the Artbase would require selecting one of the
> qualifying free licenses as described by the FSF
> (http://www.fsf.org/ licensing/licenses/index_html). I don't
> feel that Rhizome would have any obligation to describe the
> differences between the licenses.
> Owners of the code should determine that themselves before
> submitting. Another thing that would be interesting is that
> if someone creates a new project using code from the
> repository and then submits that work to the Artbase, they
> should indicate that open Artbase code was used and what code
> it was. That way we'll end up with a big reference list of
> different ways that the code is utilized. Also, if someone
> makes significant changes to existing code, that code could
> be resubmitted to the Artbase with a link to the code that it
> was derived from so that you get some sort of historical code tree.
>
> On top of everything else, I really think that this could
> also help to introduce the general public to some of the
> processes and methods involved in the creation of digital and
> networked art. The more I think about it, the better I like it.
>
> As Joseph has suggested, there do exist several web-based
> systems for organizing and archiving open-source projects but
> I'm not really sure that that's the way to go. Firstly, most
> of them are really ugly.
> Created by computer nerds with absolutely no sense of visual
> aesthetics. Secondly, they tend to be "all encompassing"
> whereas I think it might be easier for Rhizome to begin with
> a rather simple implementation, utilizing as much of the
> Artbase's current architecture as possible and then adapt,
> add and alter as time goes by and as we learn what works,
> what doesn't, what's good, what's bad, etc.
>
> best,
> Pall
>
> On 4.4.2006, at 00:52, Lauren Cornell wrote:
>
> > Hi Pall, This is an interesting idea. How do you think such a
> > repository could be mapped onto or integrated with the
> ArtBase as it
> > currently stands?
> > Lauren
> >
> > On 4/3/06 12:03 AM, "Pall Thayer" <p_thay@alcor.concordia.ca> wrote:
> >
> >> A short explanation and reasoning follow but the
> suggestion is for a
> >> repository of open-sourced code by artists.
> >>
> >> More and more, internet-based artwork has come to rely on server-
> >> specific technology. Therefore it appears to me (this is based on
> >> some very quick browsing) that fewer works are actually being
> >> preserved in the Artbase and more projects are simply
> being linked to
> >> from it (as opposed to 'cloned' work). A repository for
> open-sourced
> >> code that is used to run some of these server-specific
> projects would
> >> serve to rekindle the idea of the Artbase as a 'preservative'
> >> archive.
> >>
> >> Such a repository would also serve as an invaluable
> resource for the
> >> sharing and dissemination of knowledge. I would suggest
> that the code
> >> need not be complete and compilable or usable in and of itself. It
> >> could be functions or snippets of code as well that could
> easily be
> >> incorporated into a variety of projects (i.e. "Here's a
> little Perl
> >> function I use when I have to scale numbers into a certain
> range.",
> >> etc.).
> >>
> >> I think that this would be a good move and that it would
> benefit the
> >> community. It would be interesting to hear what others think about
> >> it.
> >>
> >> Pall Thayer
> >>
> >> --
> >> Pall Thayer
> >> p_thay@alcor.concordia.ca
> >> http://www.this.is/pallit
> >>
> >>
> >>
> >>
> >> +
> >> -> post: list@rhizome.org
> >> -> questions: info@rhizome.org
> >> -> subscribe/unsubscribe: http://rhizome.org/preferences/
> >> subscribe.rhiz
> >> -> give: http://rhizome.org/support
> >> +
> >> Subscribers to Rhizome are subject to the terms set out in the
> >> Membership Agreement available online at http://rhizome.org/info/
> >> 29.php
> >
> > +
> > -> post: list@rhizome.org
> > -> questions: info@rhizome.org
> > -> subscribe/unsubscribe: http://rhizome.org/preferences/
> > subscribe.rhiz
> > -> give: http://rhizome.org/support
> > +
> > Subscribers to Rhizome are subject to the terms set out in the
> > Membership Agreement available online at http://rhizome.org/info/
> > 29.php
> >
>
>
>
> --
> Pall Thayer
> p_thay@alcor.concordia.ca
> http://www.this.is/pallit
>
>
>
>
> +
> -> post: list@rhizome.org
> -> questions: info@rhizome.org
> -> subscribe/unsubscribe:
> http://rhizome.org/preferences/subscribe.rhiz
> -> give: http://rhizome.org/support
> +
> Subscribers to Rhizome are subject to the terms set out in
> the Membership Agreement available online at
> http://rhizome.org/info/29.php
>
way to work it out into details. It certainly would help to get the feeling
of accomplishing sth as part of the community...
Best,
dv
> -----Oorspronkelijk bericht-----
> Van: owner-list@rhizome.org [mailto:owner-list@rhizome.org]
> Namens Pall Thayer
> Verzonden: maandag 3 april 2006 18:55
> Aan: Lauren Cornell
> CC: rhizome
> Onderwerp: Re: RHIZOME_RAW: I have a suggestion for Rhizome...
>
> Hi Lauren,
> Well, hopefully, owners of some of the work currently in the
> Artbase, linked or cloned, would contribute the code for that
> work and the code would be linked to the work (i.e. "This
> code is used in ..."). I can't decide whether it should be a
> requirement that the code belong to a piece in the Artbase or
> not. I think that would make it more relevant. And just to
> make sure no-one freaks out, I'm not by any means suggesting
> that everyone with work in the Artbase release their code. It
> would be entirely voluntary and wouldn't even have to be all
> the code. If I recall correctly, the Artbase already contains
> keyword references for most major programming and scripting
> languages. I think it would be good if code could be viewed
> online as a text file instead of having to download
> everything but that could be problematic for projects that
> contain several different files.
> Submission to the Artbase would require selecting one of the
> qualifying free licenses as described by the FSF
> (http://www.fsf.org/ licensing/licenses/index_html). I don't
> feel that Rhizome would have any obligation to describe the
> differences between the licenses.
> Owners of the code should determine that themselves before
> submitting. Another thing that would be interesting is that
> if someone creates a new project using code from the
> repository and then submits that work to the Artbase, they
> should indicate that open Artbase code was used and what code
> it was. That way we'll end up with a big reference list of
> different ways that the code is utilized. Also, if someone
> makes significant changes to existing code, that code could
> be resubmitted to the Artbase with a link to the code that it
> was derived from so that you get some sort of historical code tree.
>
> On top of everything else, I really think that this could
> also help to introduce the general public to some of the
> processes and methods involved in the creation of digital and
> networked art. The more I think about it, the better I like it.
>
> As Joseph has suggested, there do exist several web-based
> systems for organizing and archiving open-source projects but
> I'm not really sure that that's the way to go. Firstly, most
> of them are really ugly.
> Created by computer nerds with absolutely no sense of visual
> aesthetics. Secondly, they tend to be "all encompassing"
> whereas I think it might be easier for Rhizome to begin with
> a rather simple implementation, utilizing as much of the
> Artbase's current architecture as possible and then adapt,
> add and alter as time goes by and as we learn what works,
> what doesn't, what's good, what's bad, etc.
>
> best,
> Pall
>
> On 4.4.2006, at 00:52, Lauren Cornell wrote:
>
> > Hi Pall, This is an interesting idea. How do you think such a
> > repository could be mapped onto or integrated with the
> ArtBase as it
> > currently stands?
> > Lauren
> >
> > On 4/3/06 12:03 AM, "Pall Thayer" <p_thay@alcor.concordia.ca> wrote:
> >
> >> A short explanation and reasoning follow but the
> suggestion is for a
> >> repository of open-sourced code by artists.
> >>
> >> More and more, internet-based artwork has come to rely on server-
> >> specific technology. Therefore it appears to me (this is based on
> >> some very quick browsing) that fewer works are actually being
> >> preserved in the Artbase and more projects are simply
> being linked to
> >> from it (as opposed to 'cloned' work). A repository for
> open-sourced
> >> code that is used to run some of these server-specific
> projects would
> >> serve to rekindle the idea of the Artbase as a 'preservative'
> >> archive.
> >>
> >> Such a repository would also serve as an invaluable
> resource for the
> >> sharing and dissemination of knowledge. I would suggest
> that the code
> >> need not be complete and compilable or usable in and of itself. It
> >> could be functions or snippets of code as well that could
> easily be
> >> incorporated into a variety of projects (i.e. "Here's a
> little Perl
> >> function I use when I have to scale numbers into a certain
> range.",
> >> etc.).
> >>
> >> I think that this would be a good move and that it would
> benefit the
> >> community. It would be interesting to hear what others think about
> >> it.
> >>
> >> Pall Thayer
> >>
> >> --
> >> Pall Thayer
> >> p_thay@alcor.concordia.ca
> >> http://www.this.is/pallit
> >>
> >>
> >>
> >>
> >> +
> >> -> post: list@rhizome.org
> >> -> questions: info@rhizome.org
> >> -> subscribe/unsubscribe: http://rhizome.org/preferences/
> >> subscribe.rhiz
> >> -> give: http://rhizome.org/support
> >> +
> >> Subscribers to Rhizome are subject to the terms set out in the
> >> Membership Agreement available online at http://rhizome.org/info/
> >> 29.php
> >
> > +
> > -> post: list@rhizome.org
> > -> questions: info@rhizome.org
> > -> subscribe/unsubscribe: http://rhizome.org/preferences/
> > subscribe.rhiz
> > -> give: http://rhizome.org/support
> > +
> > Subscribers to Rhizome are subject to the terms set out in the
> > Membership Agreement available online at http://rhizome.org/info/
> > 29.php
> >
>
>
>
> --
> Pall Thayer
> p_thay@alcor.concordia.ca
> http://www.this.is/pallit
>
>
>
>
> +
> -> post: list@rhizome.org
> -> questions: info@rhizome.org
> -> subscribe/unsubscribe:
> http://rhizome.org/preferences/subscribe.rhiz
> -> give: http://rhizome.org/support
> +
> Subscribers to Rhizome are subject to the terms set out in
> the Membership Agreement available online at
> http://rhizome.org/info/29.php
>
NE_31032006/N
dju klapt het paard op de boer
alles is weg tragisch alles
is weg tragisch de alles is de
tragisch traag is alles liep de
weg tragisch alles de liedjes
tralies tralalalies is de wegweg
de trage de visch de weg de liep is
de maag is de tragisch de lied
is de wegweg is tragisch de man
is de mand is de heg is de weg
is zo tragisch zo sliep & zo slipe
is de way is het hoge is het wegen
is de kar op de wegen, de trage visch
de man is de maan is de tragisch
& alles de tragisch zo alles zo wit is
de is de is de einder de is de visch is
alles de tragisch de weg de is de alles
dv @ Neue Kathedrale des erotischen Elends
http://www.vilt.net/nkdee
alles is weg tragisch alles
is weg tragisch de alles is de
tragisch traag is alles liep de
weg tragisch alles de liedjes
tralies tralalalies is de wegweg
de trage de visch de weg de liep is
de maag is de tragisch de lied
is de wegweg is tragisch de man
is de mand is de heg is de weg
is zo tragisch zo sliep & zo slipe
is de way is het hoge is het wegen
is de kar op de wegen, de trage visch
de man is de maan is de tragisch
& alles de tragisch zo alles zo wit is
de is de is de einder de is de visch is
alles de tragisch de weg de is de alles
dv @ Neue Kathedrale des erotischen Elends
http://www.vilt.net/nkdee
t is 4 trees
pictures of 1-2 year old and fresh treecuts
(we went walking in nearby woods yesterday)
http://www.vilt.net/nkdee/tisfortrees.jsp
dv
(we went walking in nearby woods yesterday)
http://www.vilt.net/nkdee/tisfortrees.jsp
dv
NAGNAG ni haltnie
patacathedrat[r]ap - http://www.vilt.net/nkdee/vis4vessel_pata.jsp
... vidlege iksnip nec cunilingua tutta Ingles
ac macmac tresposti tutta cmopnrenne
vidleget procproc nun, ac fatifact 123...
hodie ulteraulteraultera prrt=0!
gold: http://vis4vessel.blogspot.com/
gold: (linguacuni Ingles): http://www.vilt.net/nkdee/vis4vessel.jsp
sneesni grat,
dv@vilt.njet
... vidlege iksnip nec cunilingua tutta Ingles
ac macmac tresposti tutta cmopnrenne
vidleget procproc nun, ac fatifact 123...
hodie ulteraulteraultera prrt=0!
gold: http://vis4vessel.blogspot.com/
gold: (linguacuni Ingles): http://www.vilt.net/nkdee/vis4vessel.jsp
sneesni grat,
dv@vilt.njet