Audiobook Cutter is an easy-to-use tool which splits large MP3 audiobook files into smaller ones without re-encoding. The split points are determined automatically based on silence detection. Because of this feature, long audiobook recordings can be cut into manageable albums with just a few clicks. The cutter is applicable for all kind of spoken content.

The main purpose of this MP3 splitter is to make audiobooks, analog recordings of speech or long podcasts more manageable in a user-friendly way: The split files can easily be used on mobile MP3 players because of their small-size and their duration allows smooth navigation through the book. Additionally the application is good accessible for visually impaired users. Audiobook Cutter supports screen readers and screen magnifiers...

Palo Alto based startup SearchMe has kept a low profile since being founded in March 2005. The company, which has 17 employees and raised $5 million from Sequoia Capital over two rounds, will launch a number of what founder Randy Adams calls “long tail search engines” in the near future. The first product they are launching is WikiSeek, which went live about an hour ago and will be officially announced on Wednesday.

WikiSeek is a search engine that has indexed only Wikipedia sites, plus sites that are linked to from Wikipedia. It serves two purposes. First, it is a much better Wikipedia search engine than the one on Wikipedia (and has been built with Wikipedia’s assistance and permission). Second, the fact that it also indexes sites that are linked to from Wikipedia means that, presumably, it will return only very high quality results and very little spam. It won’t show every relevant result to a query, but it will certainly give a good overview of a subject without all the mess.

The search results also include a tag cloud which contains Wikipedia categories containing the search term. Results can be quickly filtered by clicking on one of those categories (see screen shot, click for larger view). The first three results of a query are always Wikipedia content (unless there are not three results) and are shaded blue. The remaining results are below the shaded area...

It's long been known that spammers sell victims' addresses to each other. Keep that in mind as you look at the map... and remember that — despite their cries of "Permission Marketing Works!" — I have not given my email address to a single one of the companies that appear on the Spamdemic Map, nor have I given them permission to send me email... yet nearly all of them seem to have one or more of my addresses, and most are spamming me. Items in black on the map indicate entities that have spammed me or are involved in supporting the spammer; grey indicates companies that haven't spammed me, but may now have my address, due to their relationships with the spammers; green indicates ownership; dashed lines indicate tentative connections. First, take a gander at the Preview Image. Then brace yourself, and step into the Full-Size Version. (Don't forget your waders.) I'll soon have a more in-depth explanation of what's going on... I also hope to try to track the actual flow of each of the spammed addresses amongst the spamhausen. But right now, I need some sleep. Have fun... and don't say I didn't warn you! BTW— Due to popular demand, I've made the Spamdemic Map available as an EPS file for the sake of printing (see links above). The map measures about 62" x 41", with the smallest type at 8.8pt. If enough requests come in, I may consider selling prints, since few people are able to print at or even near that size. Have fun! ...

Of all the shows in Channel 102's original prime time lineup, "Gemberling" lasted the longest -- a full eight episodes, the final one weighing in at over 17 minutes as a self-cancelling epilogue to the adventure series. A nerd-culture pastiche drawing heavily from "Tron," "Star Wars," and "Troll 2," it was the most dependably funny, best-paced show in 102 history when it ended. It will be fondly remembered by Channel 102's creators and fans. The good news is that there may be some feature-length action for Ken Gemberling in the very near future. "Gemberling" was produced by John Gemberling & Curtis Gwinn.

Every once in a while, one of the forums dedicated to the business of software spits up a question regarding the proper duration for a time trial. It has become somewhat commonplace to expect a 30-day duration from a trial version. Some software shops package that up with functional limitations, some don't, but the time trial has proven to be the goto guy for use in a demo release. 

But the question remains — how long should the time trial be? Is 30 days something that is used because it has a proven track record, because it's what customers expect, or because developers, after focusing for months or years on building the actual product, simply decide to stick with the norm without giving the business side of their business a second thought?

I'm tempted to say the last one would pull the most weight. Such as the case with user interfaces, payment processing, pricing structure (don't get me started), and even customer support, thought given to the time trial seems to take a back seat…especially with shops releasing their first application.

Do you have trouble visualizing product sizes when shopping online? If so, try this easy comparison tool