[NetBehaviour] Backups are not enough!

[info]

marc garrett a probablement écrit :
> It's funny, I love HTML - sometimes I wish for the days when one can
>  just upload a simple page of HTML. But because we are now all
> socially networked, the threat of others (hackers, spammers) taking
> advantage of possible flaws and weaknesses in the systems are much
> higher. We also change passwords but no matter how safe we think a
> system is sooner or later some bugger comes along and proves that you
> were deluded, to think such a thing.

i think this discussion raises another issue: the content relies on the 
context. Even if data are backed-up, if the system become unable to read 
it, what remain from the content? this is a question about art, the 
relation between art and history. I know people, and i did myself, some 
pieces which where quite invisible and then destroyed, things can 
totally disappear, even on the net. but the main difference between an 
object , let's say a painting (oil on canvas), and a dataset for example 
(binary 64), is that even the context is changing, the painting remains 
but the dataset is becoming rapidly something else than thought when 
created...
I've read somewhere that the best solution to keep a binary artwork in 
it's original form is to keep it 'alive', meaning it must always be 
circulating on different networks with connected people knowing the 
original aspect and the present context in order to keep the relation 
between both.
It means you can not create now (within networks) like you create before 
(with oil), you now should take care of the context (environment) before 
thinking about the object you're working on. what does it mean? i don't 
know, but it seems we won't go back to prior art practices (they always 
can be included within present forms), but we have also to think giving 
other forms to networked art practices. Backups are not enough!

i hope this is understandable, if not , i'll write it in french :-)
let me know...

a+
yann


> The most important thing really is to have back ups, copy of the
> whole server so everything can be put back up again. Even this takes
> time.