[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [dist-obj] Ubiquitous Virus (was: The Future's so bright...)
- To: "email@example.com" <firstname.lastname@example.org>, "'Dmitri Kondratiev'" <email@example.com>
- Subject: RE: [dist-obj] Ubiquitous Virus (was: The Future's so bright...)
- From: Philip Eskelin <firstname.lastname@example.org>
- Date: Fri, 12 May 2000 03:58:22 -0700
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- Mailing-List: contact email@example.com; run by ezmlm
Yeah, all good stuff . . . but I say we FUCK the "I Love You" virus and we FUCK Neal Stephenson and we FUCK Microsoft! My responses were centered around what really might happen next. What should happen next? I don't know. Moreover, I am secure with the fact that my own thoughts on that topic have little to do with its outcome.
Right now I am banking my Vegas dollars on a future that does not change what we have today, but instead *extends* it. Think of the logical 7 OSI layers. Provide another 8th layer on top of that which allows you to program applications that use components available on the Internet right now. Dialtone access to core services like a message bus, a directory, some form of access control services, and the ability to know what's up with your applications as they use it.
I'm talking about bringing non-static services to the edge of the Internet. Akamai is providing fast access to static HTML pages and static images and static streaming media (still static -- one file being played to a client). But more is needed. Right next to the nodes that connect into the Net, meta services could exist that help coordinate fast access to all the messaging- and directory-related activities that facilitate all the non-static activities on the Internet.
Certain issues arise. In building additional layers on top of the Internet, data "storms" arising from circular publish-subscribe-publish relationships, and data "jams" arising from too many services directly or indirectly trying to access other services. So we need to establish programmer best practices which prevent the network from getting into this situation.
From: Dmitri Kondratiev
Sent: Wednesday, May 10, 2000 7:18 PM
Subject: Re: [dist-obj] Ubiquitous Virus (was: The Future's so bright...)
I think that this is not only M$ technology problem.
Virus concept (note capital letters: Virus) is much
bigger then that and as any concept evolves along with
ubiquitous networking, and mobile 'smart' things which
may be mobile smart/half-wit virus-things. The later
ones may form swarms, floks, colonies, etc.
In fact, technically there is no difference between
'good' and 'evil' mobile artificial half-wits (if I
may say so) or AWits but implications...
So, for example, in future ant-virus systems we start
talking about armies of good and evil AWits (TM) (or
'mites' using Neal Stephenson terminology) continuesly
cooperating and fighting on the Net which ineavitably
leads us to completely different computational
paradigm. This is no big news actually, interesting
part though is that we are just entering this era...
So you can view ILOVEYOU as a dinosaur in prehistoric
era of artificial mites (I like AWits better, may be
because I just cooked this word myself :)
To manage your subscription, mailto:firstname.lastname@example.org
Archives, FAQ, etc. http://www.distributedcoalition.org/mailing_lists/