[tor-project] [TSoP] stem.client - status report #1
dmr-x at riseup.net
Tue May 29 05:06:49 UTC 2018
This is my first status report for the stem.client TSoP project .
A lot of these first two weeks has been improving development processes,
workflows, and coordination.
A new Trac keyword "dev" now exists for stem tickets related to
I'll be adding more and addressing some of these soon.
I continued some work on the stem.control caching behavior, to wrap up
#25821  and tie out a remnant event into a new ticket, #26129 .
I've been planning out some of the architecture/design of stem.client
, as well as reviewing existing code .
For the former, I'm especially considering how to make stem.client most
useful within the Tor and Python ecosystems.
I've looked at the "sans-io" style in hyper-h2 that meejah mentioned
, along with similar resources .
I've also been looking at a few of the modules in the Python stdlib and
projects in the ecosystem, to try to understand their potential
# What's next
For both architecture and code review, I have a bit more work to do.
I'll confer further with Damian for these.
Architecture discussion will be started on a private pad and then opened
up to the larger community.
Afterwards, I'll be moving onto these cells:
And then I'll be working on CERTS, AUTH_CHALLENGE, NETINFO cells and the
# Other Tor things
I'd like to point out some other Tor things I'm doing, too, that aren't
under the scope of stem :).
I've had some mild involvement in the University of Michigan getting
their exit node  up and running again.
And Cryptoparty Ann Arbor will be having an event on Sat., June 9th, at
the public library. 
As with before, I've been active and reachable over IRC, where my nick
I'm still attending the network-team meetings, and since I've been
asking some clarifications on the tor-spec , I'll probably be more
chatty in those soon, too!
Please don't hesitate to reach out to me via IRC or email.
More information about the tor-project