Implementations

The original trifecta of servers can be found in defnull’s pixelflut repository.

TODO: performance comparisons would be interesting to add here.

Network separation

It is generally recommended different network from the regular event network, to prevent using all available bandwidth. Also try to prevent people from acccessing the server over a Wi-Fi connection.

Connections over the internet

Some Pixelflut servers allow incoming connections over the internet. This is something you can consider, but do it carefully. Make sure your uplink does not become fully saturated and that you shut down the server when there is nobody there to monitor the canvas.

Moderation

Keep an eye on the server at all times. Shut down the server if inapproprite content is being Pixelflutted. Blocking IPs is generally not viewed as realistic since it is far too easy to circumvent and users are highly technical.

HTTP on Pixelflut port

Some Pixelflut servers support a HTTP server on the Pixelflut port. This allows the administrator to distribute a single hostname and TCP port, which can both be used for Pixelflutting and reading the instructions in a web browser.

*.pixelflut.org subdomains

You can get a pixelflut.org subdomain too for the event you’re hosting the server! Contact Eloy or kleines Filmröllchen and they will set up subdomain records. Please also specify for how long your event runs, so we can remove the addresses again afterwards. If you have some other neat idea for a subdomain, please tell us!