PUBLIC MARKS with search designelectricalrating(capacity)net

"China has always insisted upon a policy of self-sufficiency in grain. Instead of purchasing piles of land in Africa, it has, to the best of its ability, offered aid in agricultural technology to African countries and helped their agricultural production, as well as boosted the indigenous exploitation of their own natural resources and the capacity to cope with climate change and food security," Foreign Ministry spokesman Hong Lei told a daily news briefing in Beijing.

This has prompted a great deal of innovation, but also a complexity, speed and capacity for amplification that makes the world a difficult and dangerous place for many organizations and human-made systems designed for a slower and simpler era.

over 14 million tons – about 16 years’ worth of garbage according to how much is typically accumulated in the prefecture each year. Rubble from the earthquake adds another couple million tons. The prefecture only has the capacity to dispose of roughly 0.8 million tons per year,

But another interesting implication here is what would happen (or will happen) when the majority of vehicles are electric? If our use is typical, it means about a 25% increase in electricity consumption just for transportation. What does that mean for the electricity infrastructure? Would we be able in the U.S. to add 25% more capacity in say 10 years without resorting to coal? How much of that increase can be met through conservation?

Réduire notre utilisation des énergies fossiles, c'est augmenter notre consommation électrique. Produire suffisamment d'électricité (et la distribuer) pour arriver au même niveau de confort est un problème qui reste à résoudre.

Network Realism is writing that is of and about the network. It’s realism because it’s so close to our present reality. A realism that posits an increasingly 1:1 relationship between Fiction and the World. A realtime link. And it’s networked because it lives in a place that’s that’s enabled by, and only recently made possible by, our technological connectedness.

The growth of information acquisition, storage and retrieval capacity has led to the development of the practice of lifelogging, the undiscriminating collection of information concerning one’s life and behaviour. There are potential problems in this practice, but equally it could be empowering for the individual, and provide a new locus for the construction of an online identity. In this paper we look at the technological possibilities and constraints for lifelogging tools, and set out some of the most important privacy, identity and empowerment-related issues. We argue that some of the privacy concerns are overblown, and that much research and commentary on lifelogging has made the unrealistic assumption that the information gathered is for private use, whereas, in a more socially-networked online world, much of it will have public functions and will be voluntarily released into the public domain.

Real things in the real world have a different (different, not ve or -ve) value to digital assets, and have a different capacity to surprise and delight. And physical instantiations of the digital can be both archives and souvenirs

karl says:

March 2, 2010 at 11:07 am

In your paragraph

“one of the axioms of the web that URIs are opaque, and that machines “should not look at the contents of the URI string to gain other information”, but there are lots of ways in which humans don’t follow this principle”

Not only humans in fact. The first item in your list is talking about Google and it has changed a lot the way the Web is made. In commercial environments (aka Web Agencies), SEO (capacity of having a better findability) touches the content organization but also the words in URIs. So often the SEO person will not only recommend the way to architect content in the page, but also the words that must be in the URI. It is basically an additional constraint to the list you created.

* Persistence

* Readability

* Findability

What!?

600 Tweets per second!?

...

Wow... I'm more than incredibly underwhelmed... I mean I kind of imagined Twitter had all these scalability problems to solve because they had thousands or maybe even hundred thousands of tweets per second.

Heureusement, les places de marché n'ont pas attendu Ruby pour être développées... (hop un lien pour donner un ordre de grandeur (note : mps = messages par seconde)

There are two ways to add capacity. We could do this by adding more computers (memcached servers). But we can also change the software that talks to Memcached to be as efficient with its requests as possible. Ideally we do both.

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business.

A significant weakness of HTTP in my view is its dependence on the MIME standard for media type identification and on the related iana registry. This registry is a limited bottleneck that does not have the capacity to deal with the media type definition requirements of individual enterprises or domains. Machine-centric environments rely in a higher level of semantics than the human-centric environment of the Web. In order for machines to effectively exploit information, every unique schema of information needs to be standardised in a media type and for those media types to be individually identified. The number of media types grows as machines become more dominant in a distributed computing environment and as the number of distinct environments increases.

Even more likely, they were gawking at a very, very large scoreboard — the 160-foot-long, 1.2 million pound, Mitsubishi Diamond Vision true HD display, that is the centerpiece of Cowboys Stadium. This is a spectacular object, this scoreboard. It cost, by itself, twice as much to build as the previous Cowboys Stadium. It is maintained via a ten-level internal scaffolding system and its use requires the services of a full-time, highly trained operations team. Its display capacity is equal to 4,920 52-inch flat panel televisions, and it is illuminated by 30 million pulsing light bulbs. In short, it makes your typical Jumbotron look like a 13-inch TV/VCR.

NEBULA is a Cloud Computing environment developed at NASA Ames Research Center, integrating a set of open-source components into a seamless, self-service platform. It provides high-capacity computing, storage and network connectivity, and uses a virtualized, scalable approach to achieve cost and energy efficiencies.

The fully-integrated nature of the NEBULA components provides for extremely rapid development of policy-compliant and secure web applications, fosters and encourages code reuse, and improves the coherence and cohesiveness of NASA's collaborative web applications. It is used for Education and Public Outreach, for collaboration and public input, and also for mission support.

Built from the ground up around principles of transparency and public collaboration, NEBULA is also an open-source project. NEBULA is built on the NEBULA platform.