It's alive in tor now too: ws://m2swjvhhbxcctnesbwwkqruwlz2fmlbi2u5cyulp7gzzi7pvjj42otqd.onion
That said, since .onion totally allows TLS even via let's encrypt, I will probably put this behind Caddy later and enable HTTPS support. But: It resolved and responded WAY faster! And immediately too, i2p actually needed two tries to get the first connection to work.
Will do the Caddy linkage in a bit; curious to see how it's auto TLS handles onions.
Oh, nice, you can probably add them into 0xtr onion relay repository list 👀
https://github.com/0xtrr/onion-service-nostr-clients
Why do you want to add extra TLS? Is it for benchmark? I think it only add extra overhead in encryption while only gain minimal benefit. Nostr relay seems doesn't really need double encryption because its data already protected with signature 😅
https://blog.torproject.org/tls-certificate-for-onion-site/
Did LetsEncrypt announce their support for .onion TLS certificates? Probably i missed them, i thought it was still in draft?
