For some highly confidential environment, or for some user who want to reduce the binary size by dropping the content which they would never use, It would awesome to capsule sharing-related functionalities which described in https://docs.asciinema.org/getting-started/#sharing , as an cargo feature in Cargo.toml . To have less impact for majority users, it could include this feature in default features.
For user who just want to record and playback without any other internet upload and sharing activities, can pass --no-default-features in cargo build .
Interesting idea. So, asciinema 3.0 doesn’t do any uploading by default, and asciinema upload command now requires explicitly choosing an upload server (e.g. asciinema.org) on first use. I assume that this is not sufficient for your use case.
A cargo feature is something that would work here indeed, but I’d rather keep things simple, and toggles like this introduce conditionals (compile-time, but still).
There wasn’t much ask for such feature stripping so far, but I’m open to revisit this idea in the future. Meanwhile, I encourage you to disable those features in your own fork (since you’re willing to build from source anyway).