Brandymore Castle

The issue of whether people should pay for forums or not came up on dpreview . With the current economy, I expect how to pay the bills will be a growing question for many web services. The problem is with forums there is perfect competition. Anyone can setup a forum and run it for next to nothing. If one forum decides to charge a fee, the users can flee to another forum. The only reason they might stay is because of the audience. For example, photographers pay for to host their photographs on Flickr primarily because it provides a rich audience of people who love to look at still photographs. Flickr is the Life and Look magazine of our time, it is the revival of the great picture magazines, not because of its technology (that helped orient the site in the right direction to succeed, just look at the abject failure of Picasa to be social---too little too late). Flickr just happened to be where most people who like to look at pictures gathered, mostly because of its blog-like streams of ...

As the popularity of short, fragmentary messages grows, I have become concerned the public conversation may lose the capacity for thoughtfulness and reflection. At the same time, I would like to caution those who condemn Twitter or other systems based on micro content to not throw the baby out with the bath water. The long form newspaper article found in the New York Times or Washington Post contains a lot of material used to provide background for the reader, often at the end of the article. Not only is this text boring and redundant to the knowledgeable reader, it takes up previous space. The one thing the web is good at is connecting one piece of knowledge to a broader context of other pieces of knowledge. There is no sane reason to continue repeating background and further reading material in a long form newspaper article when on the web, a writer can simply link to the information. The brief, concise texts of micro content can be connected to many other sources of information, som...

I was prompted by something Andrew Shafer of Reductive Labs said (on the FooCampers list, so I won't reproduce it here, since it was forwarded to me) about the quality of communication among software developers. He was talking about how communicating the overall design and intentions of the project is vital, so the developers are not left guessing about how the application will be used and what its architects think it should do. What is important is the existence of a conversation between the leaders of a project and the developers writing the code. This hits very close to home, because our farmfoody.or g project is essentially there to improve the flow of information between producers and consumers of food, to enable a conversation . It occurred to me the solution is to throw away the flash cards and bulleted design specifications and just facilitate the conversation. Why not use social networking tools for developers to communicate? (You can get a sense of another approach from ...

I've been thinking about "namespaces" for tags lately. Sometimes tags become too random, disorganized, or numerous to be relevant or useful. One way of cutting through the clutter is to create more than one set of tags. I've seen this on at least one website, sprig.org, which offers "togs" or an alternative set of tags to classify posts by. The difference is these tags are restricted to a particular concept, types of ecology-related terms, such as "organic." What this secondary set of tags produces is in reality a set of tags under another namespace "Ecology." It is possible to organize tags into namespaces, each representing a concept. This would not be imposing hierarchy on tags, but creating nodes representing concepts. So that Ecology might contain organic, carbon free, sustainable, etc. and Mathematics might contain number, equation, factor, etc. I organize my photographs in Photoshop Elements using tags. I chose to avoid using tags ...

What is SpeakUp? A simple text markup language for transcripts of moving pictures or video including a markup language for annotation. Overview When the Folkstreams project required a way for filmmakers and academic contributors to create and maintain transcripts for films archived and presented through the Folkstreams website, I decided a simple text markup language would be the best way to store and edit transcripts. A transcript markup language defines a series of conventions for formatting text (like wiki text) that is translated into HTML for display. SpeakUp was designed to contain as much content as possible and preserve meaning for possible later conversion into XML or database form. Speakup is implemented as a module extending the PEAR Text_Wiki library text translation module and is a requirement for use. Although development and documentation of Speakup is not complete, it is in use on the Folkstreams website. Speakup, including all markup, code and documentation is ope...

While developing Farmfoody.org over the last two years, we came up with a very similar idea independently. Most sites designed to help you connect with local organic farms require you to search for farms in your locality. We thought that people shouldn't have to search for stuff, it should come to them automatically. If you wanted some fresh locally grown tomatoes, instead of searching for for farms with tomatoes for sale in your area, you just check your own profile to see if any of the local farms you are friends with have tomatoes available. This might be through a map of local farms or through a farm you have become friends with that has put out a bulletin about their new tomato crop. We decided that a social network was the best way to direct and filter this information to the consumer and enable them to make unexpected connections with farms and foodies whose interests and connections mirror their own. People could explore the world of small independent farms and the ...

I recently discovered a wonderful new open source project for creating Flash charts. It is open source, non-proprietary and best of all for a non-profit on a tight budge, it is free. In the last week I deployed Open Flash Charts after integrating the package into our Folkstreams content management system. For users of our system (through their personalized area My Folkstreams), this will be a great improvement in the quality of charts. We make the statistics on visitors and video views available to filmmakers, and the Flash charts are simply beautiful compared to our old ones based on phplot. You can download the code for OFC (Open Flash Charts) from their homepage. It is the work of John Glazebrook and he must be a designer, because the default charts in the tutorial are beautiful and take advantage of the interactive features of Flash. I discovered a few kinks that need working out, but overall, this is an excellent addition to the open source code making up the Folkstreams platfo...

Here is an idea I had recently for a new photo sharing application, which would make it easier for anyone to use photographs in their own context. A site is created where users can sign up. They submit the name of their Flickr photostream. The site pulls in any photos from their stream that have rights set to Creative Commons remix license. Any user of the site can select any image pulled from the users Flickr photostreams collectively. There could be a single photostream "lightbox" used to select images from, I'm not going into details here. The idea is to let any user "reframe" any image contributed to a pool of images by other users. Reframe means to give the image another context. For example, an expert on historic photographic processes might frame an image with a text explaining the history and chemistry of the process that made the photograph and how to identify an example of this type of photographic image. A family historian might frame the same image w...

I love the idea simple software. Of software without cruft and bloat. When I create an application I want to make it simple, but that is not the way of the world. Most applications end up being complex. I have not entirely given up on the idea of fighting creeping featurism, featuritis and bloat, but it occurred to me that it may be a losing battle, after switching from SimplePHPBlog to Wordpress (not for this site) and Blogger. It seems that most projects to create plain vanilla or simple versions of software with a reduced feature set nearly always fail to gain popularity. If you look at Windows, it's sold on features, when you look at products in the store, they are sold on features. When you think of the natural world, it seems true that: All significantly interesting things will necessarily become complex and paradoxical given enough time.