• Participants debated how to organize user feedback on Thingiverse project pages, noting that raw comment threads mix bug reports, legal discussions, shout-outs, and other noise, making them hard to navigate.

• The discussion weighed using a mailing list with RSS integration versus embedding a distributed bug tracker such as bugseverywhere.org, while also considering how users could manage multiple e-mail subscription streams (comments, bugs, edits, etc.).

• Semantic MediaWiki (SMW) was proposed as a single platform that could host both wiki pages and structured bug/issue data with automatic RSS feeds, but kanzure expressed strong disapproval of SMW for this purpose.

• A link to a detailed comparison of GitHub vs. Bitbucket (http://dev.pocoo.org/~blackbird/github-vs-bitbucket/bitbucket.html) was shared as background for evaluating code-hosting and issue-tracking options.

• An interactive Nature visualization ranking the most-cited scientific cities (http://www.nature.com/news/specials/cities/best-cities.html) was highlighted, with the observation that Moscow’s rank remained stable over time.

• Participants criticized the “Self-Repair Manifesto” on iFixit (http://www.ifixit.com/Manifesto) for embedding text inside graphics, making it non-searchable and bandwidth-heavy; they advocated plain-text or minimally styled versions instead.

• A side observation was made that manufacturing new items is often more time-efficient than repairing broken ones, challenging the manifesto’s core premise.