extra ports on osculator
I'm stochastic it hurts
correct lang port (+2 squashed commits)
Squashed commits:
[a43e76d] make all ports assumptions explicit; somehow this is even more broken than before
[1d83d9c] let's keep permuting the port numbers for a while, that looks like fun.
cargo cult in some other peoples' code.

Maybe that will work. Maybe then I won't have spent 20 hours on the suppsoedly easiest part of this fucking nightmare of trying to fucking do fucking IO with fucking subcollider over OpenWoundControl (+2 squashed commits)
Squashed commits:
[5ee0877] if i put lots of debugging in maybe I can make python pretty please do something nice happy? no.
[b66be78] maybe it will work if i do no client configuration whatever? no.
oops (+1 squashed commit)
Squashed commits:
[a104ba2] rename things. cast augury. recite sacred names.
remove hopefully unrelated testing thingy
tidy up my shotgun rage debugging (+1 squashed commit)
Squashed commits:
[56f7e66] double everything
get rid f quit just in case (+1 squashed commit)
Squashed commits:
[15e6cf6] mild bonus debugging (+1 squashed commit)
Squashed commits:
[2842f4b] flip miscellaneous things on and off int he graudally vanishing hope of making python receive one lone single bit of data from sclang
thready server
aaaa, only uncliented OSCServers work (+4 squashed commits)
Squashed commits:
[fbab6a6] so I've found some fragile conditions in which one server will server to approximatedly one client.
[6c09396] server with unbound client actually receives messages
[d82468e] interconnected clients and networks for weak link identification
[ee65e73] minimal OSC server to get this debugged