Giter Site home page Giter Site logo

imerge's Introduction

iMerge

Inspiration

iMerge is greatly inspired by the work ZAP, Zapped Artificial Picture, by apfab, a.k.a. Albert Westerhoff and Fabian de Boer, from 2006. Their version being written in PHP, I wanted to create a version in Node.js to see if this was both possible and if so, if it would be shorter in amount of lines of code.

What fascinated me in ZAP was the fact that the application actually creates the images, without human intervention. Or at least, ZAP originally requests user input before it starts out merging images. I wanted to have the human decoupled from the concept: I want the internet to autonomously create new images. I did this also with ax710 in Maleglitch and see this as a core feature of my artistic work: to only create blueprints and not to create images myself. I don't want to choose what an image should look like. I only want to create an outline and let the internet create the real images.

Concept

This app merges images retrieved via Google into a new image. In this case, images from artists, because it used the ars.y-a-v-a.org API to retrieve random artist names. This app is a blue print. It does nothing more than creating the outlines for a process. All resulting images are (probably) unique. They are made by the internet, on the internet, they have no copyrights, as a non-human created the image. Compare the macaque case. The code of the app is licensed under MIT, but, let me repeat, the resulting images are the product of a creative process fulfilled by the internet. The resulting images are in the public domain.

Artist names used in this app are randomly taken from an artist name api called ars. Then Google Images is requested to find images with this name. When we have a result, three images are picked and combined together into a new image.

For the curious

The node-gd package, using libgd2 is used, as it was used in the PHP version of ZAP also, and because, as far as I could see, it was the better image processing package in NPM. I store the results in public/images and return an existing imags in more or less 2 outof 3 requests so save a bit of CPU usage. Also, I cache the Google CSE (Custom Search Engine) JSON result to limit the cost, since this service unfortunately isn't free.

Contributors

License

MIT

imerge's People

Contributors

y-a-v-a avatar

Watchers

 avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.