notthisbodySat, Apr 11, 2009 A metaOS in a browser-type form as you describe it is exactly what we should be heading towards, I think. It should take a form that can be installed on any system, no matter what the OS. We do not need to reinvent the wheel but aggregate useful facets of existing and soon-to-be existing tools.
I'm not sure about the technical things - I'm not a programmer and do not know what programming language or platform would be best to build the TopOS. I'm glad that you think that it could be done in Processing, but I suppose we'd really have to put together a comprehensive technical body of research about what we need and the interoperability necessities...and choose our tools based on the needs for the functionalities we desire.
There should be a body of users steering these developments, I agree. However, what you cannot steer is the type of users who use the products of these developments. Facebook is a masterpiece from an engineering point of view, yet most of its users are "ordinary people". But let's not get off track.
That's why the architecture of the Top(OS) must be well thought out, so that it enables and encourages the 'ordinary' users to go beyond their ordinary use. I don't exactly understand how this would work myself yet. Its like...you make a product a specific way that discourages one type of use and encourages another. its not like the 'product' should be closed off and limit the use, but rather...gets fuzzy at this point. It's a fine line.
We must remove the barriers and enable, enable, enable the ordinary user to easily access the possibilities of non-superficial uses. Beyond that, it's up to the individual, and the individual can't be forced to use something a particular way, just encouraged. Our architecture must encourage.
I think there are many who are interested in collaborating in the development of the Top(OS) 0.1 (not necessary in an Amoeba form, but in multiple manifestations). I think we will get started very soon :)
A metaOS in a browser-type form as you describe it is exactly what we should be heading towards, I think. It should take a form that can be installed on any system, no matter what the OS. We do not need to reinvent the wheel but aggregate useful facets of existing and soon-to-be existing tools.
I'm not sure about the technical things - I'm not a programmer and do not know what programming language or platform would be best to build the TopOS. I'm glad that you think that it could be done in Processing, but I suppose we'd really have to put together a comprehensive technical body of research about what we need and the interoperability necessities...and choose our tools based on the needs for the functionalities we desire.
That's why the architecture of the Top(OS) must be well thought out, so that it enables and encourages the 'ordinary' users to go beyond their ordinary use. I don't exactly understand how this would work myself yet. Its like...you make a product a specific way that discourages one type of use and encourages another. its not like the 'product' should be closed off and limit the use, but rather...gets fuzzy at this point. It's a fine line.
We must remove the barriers and enable, enable, enable the ordinary user to easily access the possibilities of non-superficial uses. Beyond that, it's up to the individual, and the individual can't be forced to use something a particular way, just encouraged. Our architecture must encourage.
I think there are many who are interested in collaborating in the development of the Top(OS) 0.1 (not necessary in an Amoeba form, but in multiple manifestations). I think we will get started very soon :)