desktop-streaming VS wastebin

I'm using webrtc-rs for my personal project and their RTP stack is chock full of allocations/deallocations. I, on the other hand, prefer to use preallocated buffers so I find myself having to reimplement a lot of RTP functionalities.

Finished the native Android client of my desktop streamer and latency still sucks. I looked over at Moonlight's code and they have lots of vendor-specific hacks for lowering latency. But I can't just copy that because: 1) it's GPL, 2) I'm doing the decoder initialization purely in Rust so I don't have convenient access to the Java methods.

I found it easier to integrate NvEnc to webrtc-rs. libwebrtc is too tightly integrated and would need a massive C++ shim. Would like to see how your implementation would look.

Made a desktop streamer using Window's IDXGIOutputDuplication API and the webrtc crate.

Looks nice. I was using wastebin but will probably switch to this. I like the interface better and it also supports images/attachments, and also written in Rust!

Wastebin and lenpaste are pretty good too, and simple to run with docker.

Preparing a new release of my pastebin that now compresses text data with zstd and replaces the horrific time-based deletion mechanism with a meaningful, owner-based one.

Very early attempt at writing a basic library to syntax highlight code with HTML/CSS as the only output. It is based on tree-sitter and Helix themes and if things pan out I will use that for my minimal pastebin instead of syntect. Main motivation is faster highlighting and more available color themes.

Building the millionth pastebin because there is always something wrong with existing implementations. It's inspired by bin but uses axum and sqlite and supports expiration and dark/light mode.