pixelbox VS openssh

I include the onnx file in resources folder and use tract at runtime. You can see how it's generally used in this file: https://github.com/JosephCatrambone/pixelbox/blob/main/src/image_hashes/convnet.rs

The full source is here: https://github.com/JosephCatrambone/pixelbox/blob/main/src/ui/image_table.rs

I wouldn't recommend it, but here's my source tree if you're curious https://github.com/JosephCatrambone/pixelbox

I didn't think anything would take me away from FLTK, but I've started to default to egui for my projects. I'm still a bit of a novice, but I enjoy it. My code's a mess, but one of the more fun projects I built with it was a desktop image search app: https://github.com/JosephCatrambone/pixelbox

Released openssh-sftp-client 0.11.0 and worked on openssh-rust/openssh

In terms of the API, IMO openssh-rust/openssh offers a much more intuitive set of APIs than libssh2 and the libssh2 does not offer any async API (P.S. I only took a brief look at its doc).

Here're a few projects I considered interesting (including my own project) and relatively easy to participate: - pushgen Push-style design pattern for processing of ranges and data-streams. - compact_str A memory efficient immutable string type that can store up to 24* bytes on the stack - openssh-rs Scriptable SSH through OpenSSH in Rust - pegasus A multi-node parametrized command runner with a focus on simplicity - concurrent_arena Container that can have elements insert/removed concurrently and uses a 'u32' as key.