I wrote a small music project myself and found that the earlier Shishan glitch has been generating 3 GB of outbound traffic daily.

Because of NL my network here is terrible and access is extremely slow, so I can’t come often.


First, in the past few days I made a TreeData. I started by writing everything manually and copying some AI‑generated code from an old project, and finally used AI to write part of the CSS.
[login]

http://65.21.233.158:51040

Token: I don’t have it; my token isn’t on my phone and I can’t even remember it myself.
[/login]

The homepage mimics the style of FOFA and is adapted for mobile (one of the few mobile‑friendly pages I’ve written).


After deployment I felt the server bandwidth might not be enough.

Then I took a look at the server’s network tab.

(I discovered this the day before posting this thread, and solved the problem last night.)

At first I thought the site had been hammered.

After debugging with others for a while, we found it was a buffering connection issue in the PI part (it caches 10 WS connections to speed up users, but the proxy kept failing to cache).

I set the cache to 0, and today the traffic looks normal.

I can only say I’m sorry for the trouble caused earlier.

1 Like

Ber, where is the red envelope I set?

1 Like

How do I use this?

What is this for?

Visible after logging in; you can use it later.

1 Like

Hey, how do you play this?

A service that checks which rooms a Minecraft Bedrock Edition player has played.
Currently the time doesn’t seem accurate (reasonable error is 2 minutes, but it actually goes up to about 16 minutes).

I just passed by without looking closely to understand.

Let’s see what it is