2019-11-09 06:17:49
*https://github.com/snowblossomcoin/channels/compare/fe9ca8c16b9c...d032d3d6dad9*
https://github.com/snowblossomcoin/channels/commit/d032d3d6dad973570e0a3fce59274d2ebf51fdd8 - Socks5 relay
GitHub
2019-11-09 07:10:37
*https://github.com/snowblossomcoin/channels/compare/d032d3d6dad9...9e3646e8cc1b*
https://github.com/snowblossomcoin/channels/commit/9e3646e8cc1bcab5518c315cc907ee1f0102e4dd
GitHub
2019-11-09 07:39:28
*https://github.com/snowblossomcoin/channels/compare/9e3646e8cc1b...784e818429eb*
https://github.com/snowblossomcoin/channels/commit/784e818429ebe558a64efa5470ed247d073cec78 - Rework webset path tokens
GitHub
2019-11-09 07:39:53
Now when using the new socks5 proxy, you can go to a channel via something like: http://34tlwtvlkm8nqmt3m63au3l5g9t5njzfjdfwmxme.snowblossom.io/
Fireduck
2019-11-09 08:31:36
get yourself a wildcard cert from letsencrypt for that
Rotonen
2019-11-09 14:14:57
I was thinking about that. To be useful, I'd have to share that with everyone.
Fireduck
2019-11-09 14:15:05
So they could have the cert on their own node
Fireduck
2019-11-09 18:00:49
check out the acme dns auth mechanism
Rotonen