speckij / hochwasser Goto Github PK

Offset abuse

Most servers (pixel, pixelflut-server-dotnet, shoreline...) support
OFFSET <x> <y>

Depending on the screen size, abuse of OFFSET yields a significant efficiency increase in efficiency.
By splitting the image into blocks (e.g. 100x100 or 10x10), prepending each block with an offset command and sending relative coordinates the amount of bytes sent can be reduced.

For a 1280x720 full hex image, a block size of 100x100 yields a 12% reduction in bytes to be transmitted.
A block size of 10x10 yields a 22% reduction.
Potential efficiency gain scales with canvas size.
The theoretical maximum is yet to be determined, and further optimization is possible by dynamically adjusting block size.

When using a fixed number of connections/threads with multiple blocks being handled by one connection, the blocks need to be sent sequentially and ideally as a concatenated byte stream.

Stripped hex

When sending hex values with less than 6 digits, servers seem to behave the same and add leading zeroes. All hex values can be optimized by stripping up to 5 zeroes from the left.

Currently the command line does not support all functionality the REPL offers. Especially for automated deployments it would be useful to align both options into a central struct.

Currently missing from CLI:

• metrics
• offset rand
• rgbsplit
• txt
• rotation
• scale

Missing from REPL:

• cpuprofile not trivial nor meaningful to add

• allow for repeating commands / command history
• autocomplete

The REPL can get pretty spammy with "No connection"/"attempt failed" messages (e.g. when getting locked out because of BBR fun).

Toggling all error messages off would be quite useful else the REPL is practically unusable.

Example:

While your code is fast, it does not accurately display pictures, e.g. even this one: https://github.com/SpeckiJ/Hochwasser/raw/master/benchmarks/benchmark_x280.png

Text (e.g. "Hochwasser") is shown in red.
Tested with go version go1.11.6 linux/amd64.

Currently when connecting to a rán c&c a client has no idea of knowing what is currently being pushed.

It would be cool to see a preview of what is currently pushed by a specific machine, especially when pushing with multiple people in different physical locations. Else only the human using the c&c REPL knows.