SjonHortensius

I'm running `1.10.44` on Arch Linux which should include 8f83833 but I appear to have the same issue: ``` Thread 1 "workrave" received signal SIGSEGV, Segmentation fault. 0x00007ffff7d44387 in XQueryExtension...

apparently this is still an issue, syncing a fresh nimbus instance on a high performance machine will result in mediocre sync performance (less than 10 blocks/s) with one thread blocking...

wasm first would be a good idea as it would reduce the load as the input & results don't need to be stored and it is resistant to abuse -...

@michaelsproul you're right wrt the memory usage, I misinterpreted those. I have relevant logs - but I am unwilling to publish them unscrubbed. I'll send some parts through mail

Making examples executable would ideally be done by storing the correct script link somewhere. Alternatively a new `POST` could be done to the correct endpoint containing the full example code...

I have a POC ready - I went with iframes for the initial version. I implemented `window.postMessage` and allowed `php.net` as `frame-ancestors` in the csp. This allows an external domain...

I see your point but all of these issues can be explained: * `--help` panics because I used `panic` instead of `fmt.Printf` + `os.Exit` (I can fix this and you'd...

There seems to be some progress on this in https://github.com/Graylog2/go-gelf/tree/v2 - but apparently that still doesn't support `TLS`