Dear list, I'm writing a technical inquiry about tor-ptmgr. Although the issue #666 ( https://gitlab.torproject.org/tpo/core/arti/-/work_items/666 ) said that: " Some people would like to use pluggable transports in a context other than inside a Tor process for making Channels. Right now, ptmgr contemplates this but does not actually provide an API for it.", I saw that: ```rust #[tokio::main] asyncfnmain() ->Result<()> { tracing_subscriber::fmt::init(); letcommon_params=PtCommonParameters::builder() .state_location("/tmp/arti-pt".into()) .build() .unwrap(); letclient_params=PtClientParameters::builder() .transports(vec!["obfs4".parse().unwrap()]) .build() .unwrap(); letmutpt= PluggableClientTransport::new("./obfs4proxy".into(), vec![], common_params, client_params); pt.launch(PreferredRuntime::current()?).await?; loop { info!("message: {:?}", pt.next_message().await?); } } ``` at .crates\tor-ptmgr\examples\run-pt.rs which seems like it should actually work without tor. Does this example already intended a public API for using pluggable transports independently of Tor? If yes, why this issue is still open. I'd appreciate any clarification. Thank you. pryty26 pryty017@proton.me Sent with [Proton Mail](https://proton.me/mail/home) secure email.