2019-10-16 11:35:02
yes please

Rotonen
2019-10-16 11:35:32
also the same for everything

Rotonen
2019-10-16 12:35:03
+1 for that

Tilian
2019-10-16 12:35:39
I'm not sure if including too much network details on the simple website is a good idea (I'd prefer a separate explorer), but I can include some basics through a JSON call.

Tilian
2019-10-16 13:42:51
swagger it

Rotonen
2019-10-16 16:25:09
The entire explorer needs a rewrite. My handle rolled request handling is not clear or elegant. I wonder if there is something that can help without involving some huge framework.

Fireduck
2019-10-16 16:25:21
Having the same problem with channels

Fireduck