Overview / Usage
This document explains the website's operating mechanisms, rate limiting, caching behavior, and possible loading issues, along with guidance on multilingual usage.
The website does not restrict the number of concurrent requests, but server bandwidth and processing speed have fixed limits. Consecutive use of the browser's back button can cause cache accumulation, eventually preventing pages from loading properly.
The following sections detail the causes, triggers, symptoms, solutions, and prevention strategies.
Network Loading Mechanism
1. The website has finite bandwidth and a fixed response-speed limit, which is within normal service range.
2. Concurrent connections are not restricted; users may initiate multiple requests without being rejected.
3. Because the speed is fixed, massive concurrency does not accelerate loading; requests are queued and processed in order.
4. Each page switch, jump, or query creates a new page instance, and the browser automatically retains the history.
Cache Storage Pattern
1. By default, browsers cache visited pages to enable fast restoration when using the back/forward buttons.
2. Each page visit creates an independent cache entry in memory.
3. Pages on this site contain dynamically rendered content, so the cache size is relatively large.
4. Consecutive back-navigation does not clear the old cache; it keeps adding new caches on top.
Core mechanism:
Pressing back â clearing cache
Consecutive back = continuous cache accumulation
When the threshold is reached = memory full = page cannot load
Multilingual & Translation Support
Regarding administrator maintenance capacity:
This site is maintained by an individual with limited time and energy. Currently, only the homepage and some core pages offer complete multilingual versions (Simplified Chinese, Traditional Chinese, English). Other pages (including this documentation) may be provided in Chinese only, or not fully translated yet.
How to use the built-in browser translation:
If you encounter a page not in your preferred language, we strongly recommend using the automatic translation feature of modern browsers instead of waiting for manual updates.
- Chrome / Edge: Right-click on the page and select "Translate to English" (or your target language), or click the translate icon in the address bar.
- Firefox: Install a translation extension (e.g., "To Google Translate") or use the built-in translation (available in some versions).
- Safari: Click the translation button on the left side of the address bar to translate into the device's preferred language.
- Mobile browsers: A translation prompt usually appears automatically, or you can find the "Translate" option in the menu.
These features are completely free and take effect instantly, covering the vast majority of content. Thank you for your understanding and support.
Issues & Bug Triggers
1. Trigger conditions
1. Pressing the browser's back button consecutively more than a certain number of times.
2. Jumping between pages and returning rapidly in a short period.
3. Keeping the page open for an extended time without closing it.
2. Bug symptoms
1. Page loading becomes noticeably slower.
2. Buttons become unresponsive, and the interface lags.
3. The page appears white or black, unable to render content.
4. An "out of memory" or "page overload" warning appears.
5. API requests succeed but the page cannot display the data.
Solutions (What to do when issues occur)
1. Refresh the page immediately (most effective)
Press F5 or Ctrl+R to refresh, which directly clears the accumulated cache of the current page.
2. Reopen the tab
Close the current tab and re-enter the URL to completely reset the memory state.
3. Clear browser cache (temporary fix)
Settings â Privacy & Security â Clear browsing data (cache only, do not clear passwords).
4. Restart the browser
Browsers consume a lot of memory after long sessions; a full restart releases everything.
How to Avoid These Issues
1. Minimize consecutive use of the browser's back button; avoid unnecessary repeated navigation.
2. Use the website's internal navigation links instead of relying on the browser's back button.
3. Manually refresh the page every 20â30 minutes to release cache.
4. Avoid opening too many tabs of the same website simultaneously.
5. At the first sign of slight lag, refresh immediately rather than continuing to operate.
Prevention (For long-term stability)
1. Develop a habit of regular refreshing to actively free memory.
2. Use the navigation, back, and reset functions provided within the site.
3. Avoid high-frequency, consecutive, or repeated back-navigation.
4. After a long idle period, reload the page to restore optimal performance.
5. If frequent jumps are necessary, refresh every 10 operations or so.
Summary:
Rate-limited â unusable
Unrestricted concurrency â faster with more requests
Cache accumulation = biggest risk factor
Regular refresh = the most stable way to use the site