- Eric Hunting’s follow-up emails on the “toolbook” concept included a proposal for a cooperative model to support open-source hardware development.  
- A debate arose over the commercialization of open hardware designs; ybit argued for a “build first, monetize later” ethos, while others worried about appearing “too commercial.”  
- kanzure shared a paper on mechanical-system modeling compatibility issues (http://adl.serveftp.org/papers/Compatibility%20issues%20for%20mechanical%20system%20modelling%20with%20standard%20components.pdf) and asked for feedback on pages 6–9.  
- Discussion of the “Multimachine” project highlighted the need for a single-page parts list; ybit noted the current documentation is scattered.  
- kanzure posted an early screenshot of the “omnifab” web interface (http://adl.serveftp.org/~bryan/screenshots/2009-11-02-omnifab.png) and identified “build” as a missing workflow step.  
- ybit prototyped user-registration and inventory-tracking features: users could declare owned hardware (e.g., RepRap parts) to auto-generate an inventory.yaml; kanzure pushed back, favoring free-text entry over a fixed list for scalability.  
- Web-framework choices were weighed: CherryPy’s inability to serve static files cleanly led to suggestions of Apache, lighttpd, or nginx; performance comparisons were linked (hostingfu.com, superjared.com).  
- UI/UX philosophy: fenn and genehacker argued for function over form—“it doesn’t need to look pretty, just be usable”—while kanzure defended modern styling for wider adoption.  
- Server-hosting negotiations: bkero offered a low-cost VPS in Portland (1–2 cores, 512 MB–1 GB RAM, “a couple TB” shared storage, unlimited transfer) for SKDB/omnifab hosting.  
- Spam-prevention strategy shifted from captchas to rate-limiting login attempts and providing sandboxed public APIs, aligning with minimalist, open-source values.