cyclince/emby-viewing-optimization-guide

This project is not code you run. It is a written guide, in Chinese, for ordinary viewers who watch movies and shows through someone else's Emby media server, usually one hosted overseas. It is aimed at people using a server someone else set up, not at server administrators, and it explicitly does not cover setting up Emby itself or tuning video transcoding or FFmpeg settings. The guide starts by explaining why a shared overseas Emby server sometimes streams smoothly and sometimes buffers constantly, even though nothing on the server changed. The real path from a viewer's device to the Emby server passes through home Wi-Fi, the local internet provider, cross-border links, and the overseas data center, and any of these steps can slow things down, especially during peak evening hours. It also explains why a low ping time does not guarantee smooth playback, since ping measures a quick round trip while video streaming needs a steady, continuous flow of data over a longer time. The guide then walks through two ways a regular viewer can improve their own path to the server, without touching anything on the server side. The first is a forward proxy, where the viewer picks their own proxy node, using tools like Clash, Mihomo, Shadowrocket, or a router's transparent proxy, and routes only Emby-related domains through that node instead of routing all their internet traffic through it. The second is a reverse proxy, where a separate entry point, often running on a VPS with NGINX or Caddy, or through Cloudflare, sits between the viewer and the real Emby server. The guide is careful to note that a reverse proxy only helps if both legs of the path are good, and that using a reverse proxy someone else's server did not authorize can violate that service's rules and create privacy or security risks. It also covers testing which entry point actually performs best for a given viewer, and points out that this approach does not work well for Emby setups where the video files are STRM links pointing straight to cloud storage, since in that case the reverse proxy has no effect on the actual video transfer.