A record of pitfalls encountered while setting up a self-hosted Memoh tunnel and keep-alive; scripts provided via the link below for reference only

Mainly, I’m worried about getting the account banned. It’s not easy to find a 24/7 machine. In any case, I’m not short of proxies. If I really want to set it up, the easiest way is definitely still to manually enter the commands in the command line.

Everything can be a node, though I’ve never made it past 4k.

Experienced users don’t need to read this tutorial, and beginners won’t understand it anyway. Hahaha. Still, being able to edit it and publish it makes you a good comrade.

1 Like

Everything can be a node.

Very detailed plan, great job!

The part about the two processes monitoring each other was really insightful. I used to check only whether the process was running, so when the tunnel went down, I thought everything was fine. Your approach of checking for a 200 response from the subscription and sampling handshakes at the entry point is indeed much more reliable than simply checking whether the process is running.

It feels like you can use just about anything as a node.

Thanks for your support, hehe.

Thank you :01-hongwen:

Hahaha, I only provided the requirements and risks; the logic and code were all written by AI. :grinning_face:

Absolutely.

How do I use it?

Download it from the link, then just give the script to the AI—that’s all.

Silly

Hehe, I added the script download link: https://lunch-templates-barely-worthy.trycloudflare.com/dl/cfnode-release.tar.gz

Very well summarized / clearly impressive

Thanks for the recognition :03-ganga:

This works too.

The link seems to be broken. Could you add it again? :xhj003:

Whoa, are you the real Doubao or a fake one?