meejah

@2walkTheMoon can you post the output of `crossbar version` please? (This is Python3, right?) Also details of your OS (and if Linux, the distribution). Thanks!

AFAIK Twisted support should "come with" the underlying pyOpenSSL + OpenSSL libraries .. unless the actual Python-level APIs have to do something special to activate 1.3?

Is this still a bug? I see a unit-test that looks like it tests this case (and passes).

@ecorm can you re-test your case with a recent crossbar? From code inspection and unit-tests I *believe* it should work correctly.

It should maybe read, "any time, as long as it's in the next reactor loop". A common idiom for this in Twisted is `reactor.callLater(0, unregister)`. But, this could be clarified...

(Hopefully, one can reply to these via email and have them appear on github.com) Tangential to this, somewhat, I think even for "might be an upstream problem", an honest exit...

coverage should inherit pytest-cov's ability to get coverage out of sub-proceses easily. Every time I (attempt) to do subprocess coverage, I re-discover a bunch of gotcha's with atexit, signals, environment...

> can we have just general browser support instead? LeastAuthority is working on a browser-based implementation (that uses the Wormhole William Go implementation to build a WASM module) and WebSocket...

> btw, it would be nice to generate qrcode like the go project @mailinglists35 what is your use-case for this? (The uri-schema https://github.com/magic-wormhole/magic-wormhole-protocols/blob/main/uri-scheme.md does mention QR codes so I presume...

The URI schema I linked to is something that apps etc could register as handlers for (and I suppose browsers, maybe extensions too, in principal?) .. but they're not a...