At the risk of adding to the wank
, I think that presenting DIY designs is a useful way is a really interesting challenge.
If you, too, think that sounds interesting, you may enjoy this "Everything is Miscellaneous" talk:
There are a lot of ways to begin a search. Here are just a few that come to mind, with some ideas about how each ways of seeking could be served:
* I just want to build speakers, but have no idea what to build... perhaps using my amazing powers of vision to browse a random collection of project pics will help me find a lead that I want to follow. Or some word-clouds from the text of the designs, and I'll click on some words that sound interesting to see designs where that word is mentioned.
* I want to use a specific driver... a web search serves this approach pretty well.
* I'm already familiar with many DIY designs... show me what's new, or popular.
So maybe you found an "in" and are looking at a particular design. What kind of "related" designs/builds could we show to help you continue your exploration?
* certainly other builds of the same design would be interesting
* other designs that use common drivers (or waveguides)
* other designs with similar words in their descriptions, or similar tags if we can get people to add tags (e.g. "constant directivity", "soft dome", "folded horn")
* similar specs such as driver size, cabinet dimensions, max SPL, sensitivity, crossover freq, crossover slope, with these specifics culled from the build descriptions and maintained by the community (similar to tags)
* builds the were published around the same date
* other designs by the same designer, or builders
You could algorithmically "score" other builds/designs for their relatedness, and show the top scorers with an indicator of why it's related (e.g. "also tagged with 'high sensitivity'", "also uses DNA-360", etc.). Use what people actually click on to help train and refine the relatedness scoring algorithm. Also show some randoms, so users don't get stuck in a dungeon, or if there are no strong "relateds".
So, this would basically be a web site. It is a potentially complicated undertaking, but you could start simple. I suggest making the info all community-maintained so that the burden does not fall on one person to enter it all (submit a build, add specs, tags, etc.). A "build" could be defined as a URL or collection of URLs. Maybe have some smarts to be able to crawl a thread on a web forum, so that you'd only have to enter one URL for a build thread. You'd probably also want a "design" entity, though not all "builds" would be associated with a "design". You could add metadata for the drivers, designer, builder, tags, crossover specs, etc. to these entities. You'd have to be mindful of content rights issues (who owns a build thread on a web forum?), but you can index the text from the links, show a snippet, and present the links along with their metadata. This could be an interesting project for a Computer Science student, or a software engineer that is looking for a project.