Chris, I am so very sorry about your illness, and I so very much wish you the very best, and if there is any glimmer of hope of a recovery, I would try to embrace that. In Peace, Dawn

On May 2, 2026 at 10:28 AM, Chris Enkidu-6 via tor-relays <tor-relays@lists.torproject.org> wrote:

On my last post to the group I mentioned a serious illness. unfortunately I should have said a terminal illness. I probably have a couple of weeks.Since my original post I really had no legitimate offer from anyone to take it over. Just a few time waster conversations that went nowhere. So as of now both tor-ddos and tor-relay-lists are down. Sorry to do this but I have other things to worry about and since only a limited number of people on this list know about it. Others can judge me however they like.

Thank you for reading this.

_______________________________________________ tor-relays mailing list -- tor-relays@lists.torproject.org To unsubscribe send an email to tor-relays-leave@lists.torproject.org

Hey there, Sad to here all of this, it's also sad that I probably didn't reach you in time. I tried contacting you, but didn't manage to get a hold of you. My heart goes out to you. Sincerely, Dennis Bronk. "dawn.belle.flood via tor-relays" <tor-relays@lists.torproject.org> schreef op 2 mei 2026 17:55:40 CEST:

Chris,

I am so very sorry about your illness, and I so very much wish you the very best, and if there is any glimmer of hope of a recovery, I would try to embrace that.

In Peace,

Dawn

...

On May 2, 2026 at 10:28 AM, Chris Enkidu-6 via tor-relays <tor-relays@lists.torproject.org> wrote:

On my last post to the group I mentioned a serious illness. unfortunately I should have said a terminal illness. I probably have a couple of weeks.Since my original post I really had no legitimate offer from anyone to take it over. Just a few time waster conversations that went nowhere. So as of now both tor-ddos and tor-relay-lists are down. Sorry to do this but I have other things to worry about and since only a limited number of people on this list know about it. Others can judge me however they like.

Thank you for reading this.

_______________________________________________ tor-relays mailing list -- tor-relays@lists.torproject.org To unsubscribe send an email to tor-relays-leave@lists.torproject.org

I wish you the best for the remaining time - i hope you can go without suffering! In case you still read this in time:

...

What kind of skills / ressorces areneeded to continue "tor-ddos" and "tor-relay-lists" exactly?

To which forum to I post this idea to Proposal : Use Handshake (HNS) Web 3 domain services as a decentralised alias/attestation layer for Tor onion identities. like say gerry.g3wip .onion is noy Web3. The Web3 name is just a signed pointer to the onion identity. Making .onion a Handshake TLD. That would indeed clash conceptually, because .onion is a special-use ICANN/IETF-reserved name. Use Handshake as a decentralised alias/attestation layer for Tor onion identities. Something like: gerry.g3wip TXT/DS-style record says: onion=jee3z7cpmfhcc62hhs33utyovghbyr3hlhumxwkr2zoo5mzskz5cvhqd.onion proof=signature from onion service key Then a resolver/browser/plugin can verify: 1. gerry.g3wip is owned via Handshake. 2. The record points to a long onion. 3. The onion service proves "yes, I authorised this alias". 4. User gets taken to the onion, without trusting a central shortener. I'm not proposing .onion as a Handshake namespace. I'm proposing a decentralised naming/attestation layer where a Handshake name can publish and cryptographically verify a mapping to a Tor v3 onion service, similar to how DNS can advertise service endpoints, but without replacing Tor's self-authenticating onion address. Gerry Bulger