revisit everything!

An API playground.

Description

A service is a web application that interacts with the revisit.link hub. It accepts image data that is encoded in base64, performs manipulations to the data to produce crazy glitches in the image, and returns the data back, also in base64 format. Developers are free to use whatever code stacks they want, so far have created services in a variety of technologies including node.js, go, processing, and ruby.

Once a service is online and validated, it can be publically listed in the central hub. Once it's published, people can visit hub.revisit.link to create glitch art with that service. See below for instructions on listing your service.

In order to be added to the hub, a service must follow all of the rules below. Use this project to test requests to your service, and this project to validate your service.

Specifications

  1. The following are the only REST calls the service needs to provide to users:
    • HEAD / where it can return a 200 response when we ping the server to see if it is up.
    • POST /service where JSON is posted to you in the following format:
          {
            "content": {
                "data": "data:image/jpeg;base64,<a base64 blob of the data>"
            },
            "meta": { }
        }
      and returns the following format:
          {
            "content": {
                "data": "data:image/jpeg;base64,<a base64 blob of the data>"
            },
            "meta": { }
        }
  2. All content from a service can only be accessed by that service. Content stored on the central hub will be deleted after 1 hour.
  3. Any content passed through http://hub.revisit.link cannot exceed 1 MB per data URI. But data coming from distributed services may increase to a greater size, so ensure your service endpoint can handle a size averaging between 1-3 MB.
  4. All code for the service must be open source.
  5. If any of the services violate the rules listed above, they will be removed from the central hub (or not merged).
  6. Once you are ready to include your service to the central hub, add your domain and send a pull request to this file.