Are there any tests or examples of client calls? How easy is it to take and use it now?
(by the way, if you are interested in the development, ask @kpp)
In general I'm JVM developer, rare C/C++ and Golang. Rust is a bit interesting to me, but I find it perhaps too hardcore for me. In Tox project, I would be interested to solve the problem with existence of the client messenger which can be used by a healthy person, the backend/protocol realization stuff is not very interesting to me.
Do you do it all on enthusiasm? :)
If you are familiar with C++, rust shouldn't be that hard to you.
There's a lot of similar concepts.
And what is the "onion client" from the examples? Is there support for Tor?
With high level events
There are also rust bindings we are using for the web client right now.
Note that rstox is somewhat messy and we are going to replace it with tox-rs.
*bindings to c-toxcore
Looks like the current clients like Toxic have the valid client code and it can be reused https://github.com/JFreegman/toxic/tree/master/src
I have not researched this question deeply
I do not know how much such a client is in demand in principle. And how much time I am willing to devote to it. I love the ideas of decentralization and anonymity, but I spend a lot of time on development at work and I'm a little tired.
@Tolsi take a look at https://github.com/tox-rs/tox/blob/friends/examples/echo.rs. Not that pretty but it works
We want to create both a simple API and a nice UI. Rust can be easily compiled into .wasm. So it's not an issue, just a matter of time
Do you do it all on enthusiasm? :)
No we didn't. But things changed.
@suhr same for nix
For aur there is no standard way to build packages. Usually they just add link to the package and wiki https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages
pkgver() {
cd "$pkgname"
git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
}
So updated.
@NamsooCho please try to push our tox-node image to https://docs.docker.com/docker-hub/official_images/#creating-an-official-image
pub fn spawn(self, dht_sk: SecretKey, dht_pk: PublicKey) -> impl Future<Item = (), Error = SpawnError> + Send { // TODO: send pings periodically
future::lazy(move || {
let relay_pk = self.pk;
let self_c = self.clone();
match *self.status.write() {
ref mut status @ ClientStatus::Disconnected
| ref mut status @ ClientStatus::Sleeping => *status = ClientStatus::Connecting,
_ => return future::ok(()),
}
let future = TcpStream::connect(&self.addr)
.and_then(move |socket| make_client_handshake(socket, &dht_pk, &dht_sk, &relay_pk)) // TODO: timeout
.and_then(move |(socket, channel)| {
let stats = Stats::new();
let secure_socket = Framed::new(socket, Codec::new(channel, stats));make_client_handshake(socket, &dht_pk, &dht_sk, &relay_pk) return with error type of std::io::Error.
I don’t want to change the return error type of make_client_handshake.
What is the most sound way to match these types.
spawn returns with error type of SpawnError.