No description
Find a file
index986 daae2128b3
All checks were successful
/ test (push) Successful in 1s
Rust CI / build (push) Successful in 1m5s
Update .forgejo/workflows/workflow.yaml
2026-04-13 23:26:59 +02:00
.forgejo/workflows Update .forgejo/workflows/workflow.yaml 2026-04-13 23:26:59 +02:00
src Improve stablity and maybe gif performance 2026-01-01 00:54:38 +00:00
Cargo.toml Improve stablity and maybe gif performance 2026-01-01 00:54:38 +00:00
LICENSE Initial commit 2025-12-31 18:08:31 +00:00
README.md Update README.md 2026-01-22 23:34:29 +01:00

WARNING: SEVERE VIBECODE ALERT!!! ( This project is a pure joke, made by an AI, actual person who owns the repo has no idea in rust)

PixelPizdec — Revibecoded Vibecode 🚀🦀

Blazing fast Pixelflut sender in Rust. Supports images, GIFs, multithreaded TCP, X/Y offsets, and zero remorse.

Licensed under WTFPL — Do What the Fuck You Want to Public License.


Features

  • Send static images (.png, .jpg)
  • Send animated GIFs frame by frame
  • X/Y offset support (place your pixels anywhere)
  • Multithreaded TCP connections for maximum chaos
  • Respects transparency in GIFs ( Untested )
  • Optimized with buffered writes for blazing speed

Requirements

  • Rust (1.75+ recommended)
  • Cargo
  • Internet
  • Brave router (optional)
  • Brain

Compilation Guide 🛠️

# Clone the repo
git clone "https://git.index986.link/index986/PixelPizdec-Rust" --depth 1 PixelPizdec
cd PixelPizdec

# Build in release mode (fast af)
cargo build --release

⚠️ Debug builds are for weaklings, use --release for max FPS.


Usage

# General syntax:
# ./target/release/pixelpizdec <image|gif> <ip> <port> <threads> <x_offset> <y_offset>

# Example 1 — send a static PNG at position (0,0) using 4 threads
./target/release/pixelpizdec image.png 127.0.0.1 1234 4 0 0

# Example 2 — send an animated GIF at position (100,50) single-threaded
./target/release/pixelpizdec anim.gif 127.0.0.1 1234 1 100 50

⚠️ Warning: may cause routers to scream


Tips for Maximum Fun

  • Start with 24 threads, ramp up later if server survives
  • GIFs with huge resolutions = chaos + lag
  • Use TCP, because UDP is for cowards
  • Sleep optional, but recommended if you want frames to match GIF timing

ISSUES:

  • Broken multithreaded gif sending, you can try but it will be weird
  • You tell me

License

WTFPL — Do What The Fuck You Want License See LICENSE for full unhinged legalese.