Disassembling something I can usually figure out easily, but putting it back together is not that straight forward.
Show HN: Take It Apart
41–50 of 61 posts
Re: Show HN: Take It Apart
#42If anyone is interested in the tech stack, it's based on Django under uWSGI, and all of the services run within Docker containers. Pillow wasn't fast enough for us to resize and crop images, so we have some faster custom code there, and we run all images through jpegtran for lossless compression. [I particularly like being able to crop all of the images within a guide on one page, with an easy scroll between images.]…
Re: Show HN: Take It Apart
#43Earlier quoted context omitted.
Could you use a Creative Commons licensing scheme like Stack Exchange?
It may be worthwhile for us to look into it, but everyone has their own favorite creative commons license so we risk offending people if we choose just one, and choosing multiple would likely complicate things for us in the future. IANAL, but some CC licenses, like one prohibiting commercial use are difficult to use/enforce since usage is difficult to define. Another issue is that if a creator wishes to regain contro…
That's why FOSS and CC licenses are perpetual; to avoid building on potentially shifting sands.
Re: Show HN: Take It Apart
#44Allowing video guides (linking to them, if you can't handle the bandwidth of serving them locally) on your site would also be a good idea.
Re: Show HN: Take It Apart
#45To quote a blog post I wrote in 2006 [1]: "To be fair to my parents, they did supply a vast supply of love, encouragement with my more sensible interests, pushed me in school (that was a lot of work and would have been much easier if I'd understood my personality type and learning style at the time) and provided an endless supply of items that I could take apart in an effort to satisfy my curiousity of "How this work…
A bit off topic, but time sure does fly!
Re: Show HN: Take It Apart
#46If anyone is interested in the tech stack, it's based on Django under uWSGI, and all of the services run within Docker containers. Pillow wasn't fast enough for us to resize and crop images, so we have some faster custom code there, and we run all images through jpegtran for lossless compression. [I particularly like being able to crop all of the images within a guide on one page, with an easy scroll between images.]…
For images, we used to do it ourselves but then moved to hosted images (cloudinary). Much better, and allows stateless web servers.
Firefox 29.0.1 on Linux.
Re: Show HN: Take It Apart
#47It would be cool if it had some sort of exchange for the individual parts after tear down. For instance I have an old smart phone with a broken lcd, but I'm sure the other parts are working. If I could use this site to document the teardown and sell or trade the individual components afterward for something I need on current project, that'd be epic.
That's a great idea. Fulfillment could be a problem, but maybe we could just connect people who have parts with those who need them? The best we do currently is create Octopart links for hover-over notes that are marked as components.
Re: Show HN: Take It Apart
#48Earlier quoted context omitted.
For images, we used to do it ourselves but then moved to hosted images (cloudinary). Much better, and allows stateless web servers.
The guide pages (e.g. [1]) are continually reloading for me. Maybe it's refreshing once per image load, or something, but I don't have the patience to wait. It did not reload continuously until I allowed JS on the page, which I did because JS is required to load images. Something seems broken. Firefox 29.0.1 on Linux. [1] https://www.takeitapart.com/guide/72
Images are lazily loaded, but that should be triggering a rescale. We are working to rethink the rescale functionality, so fixes and changes are coming (after this weekend's Maker Faire).
Re: Show HN: Take It Apart
#49Earlier quoted context omitted.
It may be worthwhile for us to look into it, but everyone has their own favorite creative commons license so we risk offending people if we choose just one, and choosing multiple would likely complicate things for us in the future. IANAL, but some CC licenses, like one prohibiting commercial use are difficult to use/enforce since usage is difficult to define. Another issue is that if a creator wishes to regain contro…
So what if the original creator of a guide that has been forked and edited multiple times decides to revoke the license? Wouldn't you have to delete all forks and edits? That's why FOSS and CC licenses are perpetual; to avoid building on potentially shifting sands.
Re: Show HN: Take It Apart
#50If you're interested in informational and entertaining videos of someone taking things apart, check out the EEVblog teardown series: http://www.eevblog.com/episodes/ Allowing video guides (linking to them, if you can't handle the bandwidth of serving them locally) on your site would also be a good idea.
We can handle a mixture of videos and images in our guides. Any video files selected during guide creation are uploaded directly to a user's youtube account via oauth, without leaving our site.
None on our team are great at video editing, so we haven't emphasized that capability of the site. There are a few videos in this guide to give an idea of how it could work (as a potential alternative to singular lengthy videos):