Earlier work

Kaleidobot

2015 · Creative TechnologyRole: DeveloperTools: Python, Twitter API

Kaleidobot was a small Twitter experiment that turned an image sent by a user into a kaleidoscopic composition and replied with the result.

Kaleidobot receives a photograph and returns a mirrored variation through Twitter.

Project

The complete interaction happened through a conversation with a Twitter account. Send an image to @kaleidobot, wait for it to be processed, and receive the transformed version in a reply. There was no separate app or website around it.

I coded the bot in Python using the Twitter API. Keeping everything inside Twitter made the exchange deliberately simple: the original post, the account that sent it, and Kaleidobot’s response remained visible in the same thread.

The documented examples use photographs of architecture, textiles, and a sailing ship. Kaleidobot turns each of them into a symmetrical composition by mirroring and repeating parts of the original image.

Twitter conversation showing a glass-roof structure transformed into a diamond-shaped symmetrical image. — An architectural photograph and Kaleidobot's geometric response.

Twitter conversation showing a patterned textile and its mirrored kaleidoscopic result. — A patterned textile becomes a denser symmetrical composition.

Twitter conversation showing curved wooden beams transformed into a symmetrical image. — Curved wooden beams provide the source for a mirrored architectural pattern.

Twitter conversation showing a sailing ship and a vertically mirrored response. — A sailing ship is reflected into a compact central composition.

What was created

The project produced a functioning Twitter bot that accepted photographs, transformed them into mirrored kaleidoscopic compositions, and replied directly to the sender. Twitter itself became the interface: posting an image started the interaction, and the response delivered the result.

Looking back

Kaleidobot did one thing and did it inside a platform people already knew. You sent it a photograph; it answered with another image. I still like that economy. The project did not need menus, onboarding, or a separate interface. The Twitter conversation was the product.