<p>Is it realistic or thought neccesary to develop a plugin/feature for this site, to automatically add a small info-box about a thingiverse link? An example of this is Apple's 3D touch technology. In theory, the plugin could recogize thingiverse links in questions and answers, replace the link with an image and the author/name of the project.</p>

<p>I'm also volunteering myself to help with this if there's interest. (Experience with Thingiverse API)</p>

[{'answer_id': 27, 'author': 'ArtOfCode', 'author_id': 127, 'author_profile': 'https://3dprinting.meta.stackexchange.com/users/127', 'pm_score': 3, 'selected': True, 'text': "<p>Typically, it's a better idea to wait before you try to get this kind of thing integrated.</p>\n\n<p>Enthusiasm is great in a private beta, but for the early stages, direct that enthusiasm towards the Q&amp;A. That's what'll get this site on its feet and into a successful public beta.</p>\n\n<p>When the site's more stable and running nicely, then if there's a need (or want) for a plugin like this then the discussion about it can be had.</p>\n\n<p>(On a tangent - if such a plugin is going to happen, it may well be down to SE's developers to get it done, which might make getting assistance from the people on this site difficult.)</p>\n"}, {'answer_id': 43, 'author': 'Adam Davis', 'author_id': 16, 'author_profile': 'https://3dprinting.meta.stackexchange.com/users/16', 'pm_score': 1, 'selected': False, 'text': "<h3>Technological issues</h3>\n\n<p>Stack Exchange works hard for its communities, but there is a limit. If thingiverse changes its API (which it can, and does, do at any time without notice) then anything we build on it has to be modified, and users will be very whiny until it's fixed.</p>\n\n<p>If we choose to integrate model viewing or any sort of API integration with an outside service, we will have to make sure the service provides some sort of legacy guarantee minimal API that won't change, and then we will only be able to use that.  </p>\n\n<h3>Political issues</h3>\n\n<p>I would be very uncomfortable endorsing a closed source, commercial service on this site.  There are many communities within the world of 3D printing that are very unhappy with makerbot, thingiverse, and their parent company, and encouraging users to use this service may result in pushing away some very valuable experts within the reprap world.</p>\n\n<h3>Looking to the future</h3>\n\n<p>If we integrate any sort of model library or model viewer, I strongly suggest we choose an open source project the community can heartily endorse.  We may link to outside models, but the core API should be servable by stack exchange without license or much maintenance so 1) we don't have to deal with API changes messing us up, 2) we don't rely on outside services that may change their terms of use or API, 3) we don't have to form complicated contract bound relationships with 3rd parties just to get the guarantees we'd need to convince Stack Exchange to invest in a new feature, and 4) we don't become too politically involved such that we disenfranchise users who may have very strong feelings about this subject.</p>\n\n<h3>Wait and see</h3>\n\n<p>This is the early beta.  Let's find out what people link to in questions before dedicating resources to improving the links/plug-ins/oneboxes.  It may be that thingiverse objects are linked to frequently, and that it would add value to the site to improve that experience, but it's also just as likely that thingiverse turns out to be infrequently linked and the effort spent now would essentially have been wasted.  Let's wait until we have tens of thousands of questions so we can properly evaluate what the community actually uses and needs.</p>\n"}]
['https://3dprinting.meta.stackexchange.com/questions/19', 'https://3dprinting.meta.stackexchange.com', 'https://3dprinting.meta.stackexchange.com/users/107/']