From 314336a3865c12923469bb47111118addff6d8da Mon Sep 17 00:00:00 2001 From: mfahampshire Date: Fri, 27 Sep 2024 18:29:32 +0200 Subject: [PATCH] rework intro --- documentation/docs/pages/developers/clients.mdx | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/documentation/docs/pages/developers/clients.mdx b/documentation/docs/pages/developers/clients.mdx index 8e8d76e61e..10de771993 100644 --- a/documentation/docs/pages/developers/clients.mdx +++ b/documentation/docs/pages/developers/clients.mdx @@ -1,11 +1,9 @@ # Types of Nym clients -At present, there are three standalone Nym clients: +At present, there are three standalone Nym clients. These are built as standalone binaries when building our codebase, but are most easily accessed through one of our SDKs: -- the websocket (native) client -- the SOCKS5 client -- the wasm (webassembly) client - -The wasm client can be accessed most easily via the [Typescript SDK]() TODO LINK, and websocket & socks5 functionality is available for Rust, Go, and C/C++ codebases via the [Rust SDK] TODO LINK , however the standalone client binaries are built along with the rest of the codebase for those who either wish to quickly experiment, or are programming in an unsupported language. +- the websocket (native) client - most easily accessed via the [Rust SDK]() TODO LINK and Go/C++ FFI TODO LINK +- the SOCKS5 client - most easily accessed via the [Rust SDK]() TODO LINK and Go/C++ FFI TODO LINK +- the wasm (webassembly) client - most easily via the [Typescript SDK]() TODO LINK > For information about the role that clients play within the Nym system and their role when communicating with the Mixnet, see the [Client network docs](../network/architecture/mixnet/clients).