PUBLIC MARKS with search takes

Over the past decade there has been a growing public fascination with the complex "connectedness" of modern society. This connectedness is found in many incarnations: in the rapid growth of the Internet and the Web, in the ease with which global communication now takes place, and in the ability of news and information as well as epidemics and financial crises to spread around the world with surprising speed and intensity. These are phenomena that involve networks, incentives, and the aggregate behavior of groups of people; they are based on the links that connect us and the ways in which each of our decisions can have subtle consequences for the outcomes of everyone else.

Networks, Crowds, and Markets combines different scientific perspectives in its approach to understanding networks and behavior. Drawing on ideas from economics, sociology, computing and information science, and applied mathematics, it describes the emerging field of study that is growing at the interface of all these areas, addressing fundamental questions about how the social, economic, and technological worlds are connected.

The book is based on an inter-disciplinary course entitled Networks that we teach at Cornell. The book, like the course, is designed at the introductory undergraduate level with no formal prerequisites. To support deeper explorations, most of the chapters are supplemented with optional advanced sections.

Google URL Shortener at goo.gl is a service that takes long URLs and squeezes them into fewer characters to make a link that is easier to share, tweet, or email to friends. The core goals of this service are:

* Stability – ensuring that the service has very good uptime

* Security – protecting users from malware and phishing pages

* Speed – fast resolution of short URLs

This is an enormous amount of geographic data. To put it in perspective, last week's planet was bzip2 compressed at 7.4GB, unzipping to 116GB, and occupying 113GB in a PostGIS database. The process of importing the data is very serious: even with a large Amazon instance which lets me allocate five gigabytes of RAM for the importer, the initial load takes over 29 hours.

If all you had was an email address, would it not be nice to be able to have a mechanism to find someone's home page or OpenId from it? Two proposals have been put forward to show how this could be done. I will look at them and add a sketch of my own that hopefully should lead us to a solution that takes the best of both proposals.

After observing particular subcultures and ethnic groups, Nikki S. Lee adopts their general style and attitude through dress, gesture, and posture, and then approaches the group in her new guise. She introduces herself as an artist (though not everyone believes her or takes it seriously), and then spends several weeks participating in the group’s routine activities and social events while a friend or member of the group photographs her with an ordinary automatic “snapshot” camera. Lee maintains control of the final image, however, insofar as she chooses when to ask for a picture and edits what photographs will eventually be displayed.

Although we are not comparing apples to apples, Gentoo did out-perform Ubuntu in almost every test, and sometimes by a fair margin. It does appear that optimizing for a specific CPU can yield a decent performance increase.

Of course, Gentoo offers benefits in other areas with their USE flags and being able to build a highly customized system. The question is whether the amount of time it takes is worth the benefit, and that’s a personal choice.

getElementsBySelector is a python function which takes a standard CSS style selector and returns an array of elements objects from the document that match that selector. This is a frequently used function in JavaScript - if you use a library. Its kind of meaning less to have this function in the server side - unless you are doing screen-scarping. Then its very useful. Recently, I had to work on a Django app that does a bit of screen-scrapping - so I created this function to aid me.

Most web pages include resources that change infrequently, such as CSS files, image files, JavaScript files, and so on. These resources take time to download over the network, which increases the time it takes to load a web page. HTTP caching allows these resources to be saved, or cached, by a browser or proxy. Once a resource is cached, a browser or proxy can refer to the locally cached copy instead of having to download it again on subsequent visits to the web page. Thus caching is a double win: you reduce round-trip time by eliminating numerous HTTP requests for the required resources, and you substantially reduce the total payload size of the responses. Besides leading to a dramatic reduction in page load time for subsequent user visits, enabling caching can also significantly reduce the bandwidth and hosting costs for your site.

Shoebot is a pure Python graphics robot: It takes a Python script as input, which describes a drawing process, and outputs a graphic in a common open standard format (SVG, PDF, PostScript, or PNG). It has a simple text editor GUI, and scripts can describe their own GUIs for controlling variables interactively. Being pure Python, it can also be used as a Python module, a plugin for Python-scriptable tools such as Inkscape, and run from the command line. It was directly inspired by DrawBot and Shoes. Thus, "Shoebot."

# There are meaningful “entry points” into the app - URIs. (No, I’m not going to mention the R-word.) It’s simply entirely unacceptable for a Web app to expose only a single URI, break the “Back” button, and disallow linking. Frameworks that don’t support URIs for application concepts, such as every customer, order, contact report, document etc. should simply be banned.

# Application boundaries are a concern to developers, not users. The Web is about linking stuff together, without any concern about application boundaries. There’s absolutely no reason why you shouldn’t be able to follow a link in your CRM application that takes you to a product page in your online catalog, or from a customer record to the information about when they last logged in to the Web site, or from a page that’s part of a complex business process UI to the appropriate documentation and on to the discussion group where you can tell everybody how much it sucks.

# Documents are accessible in a standard way. The idea of accessing any kind of document, such as an insurance application form that’s been scanned in, a letter sent to a business partner last year, or a contract with a business partner, by any other means than an HTTP GET is just stupid.