A multiplayer X11 canvas.
Based on the idea of pixelflut
, as seen at EasterHegg ’14.
Written directly against XRender so it should probably be pretty fast.
Version numbers approximate π.
It’s funny on so many levels, some of which come only with an understanding of the german language and more-or-less (probably less) great math and programming humour.
- IPv4 + IPv6 support
- Configurable frame rates and limits
- Configurable canvas dimensions
- Uniform or anisotropic scaling and centering
- Few dependencies / lightweight
- Slim codebase (~900 LoC)
- Alpha-transparency support
Building & Setup
- A C compiler
- (GNU) make
Configuration is done by passing arguments. Check the output of
to see what is possible.
to the system (not in any way required), run
Just run the resulting binary.
for some info on what you can do.
Within the window, press
to quit or
to clear the canvas.
By default, clients are limited to 50 pixels per frame (to change this, use the
argument), 25 frames are rendered every second (configurable with
). Clients exceeding the limits will be slowed down by default. This behaviour can be changed to one of the enforcement policies
(Disconnect clients exceeding the limits),
(Ignore additional pixels until the next frame) or
(ignore the frame limit, keep other safeguards) with the
option. Clients are allowed only one connection per host (though this can be circumvented by reasonably clever attackers). All limits and checks can be disabled (for example, for performance testing) by passing the
Lines of ASCII text commands separated by
via TCP on port
, unless you configure it differently (arguments
and the server responds with
SIZE WIDTH HEIGHT
PX X Y RRGGBB
PX X Y RRGGBBAA
to set a pixel to a hex color code.
There are some measures in place to limit the number of connections and pixels a client may have and set. Some are even configurable.
Bugs & Feedback
Please report bugs via the issue tracker.
If you use this on some kind of humungous screen or at a cool event, send me a picture ( [email protected]