|
2 | 2 | home: true |
3 | 3 | heroImage: /v2ray.png |
4 | 4 | heroText: Project V |
5 | | -tagline: Help you build an exclusive basic communication network |
| 5 | +tagline: Help you build your own dedicated communication network |
6 | 6 | actions: |
7 | 7 | - text: Quick Start → |
8 | | - link: /en_US/guide/start.html |
| 8 | + link: /guide/start.html |
9 | 9 | type: primary |
10 | 10 | features: |
11 | | -- title: Multiple entrances and multiple exits |
12 | | - details: A V2Ray process can concurrently support multiple inbound and outbound protocols, and each protocol can work independently. |
13 | | -- title: Customized routing |
14 | | - details: Inbound traffic can be sent from different outlets according to the configuration. Easily implement distribution by region or domain name to achieve optimal network performance. |
15 | | -- title: Multi-protocol support |
16 | | - details: V2Ray can open multiple protocol support at the same time, including Socks, HTTP, Shadowsocks and VMess. The transmission carrier can be set separately for each protocol, such as TCP, mKCP and WebSocket. |
17 | | -- title: Concealment |
18 | | - details: Nodes of V2Ray can be disguised as a normal website (HTTPS) to confuse its traffic with normal web traffic to avoid third-party interference. |
19 | | -- title: Reverse proxy |
20 | | - details: Universal reverse proxy support can achieve intranet penetration. |
21 | | -- title: Multi-platform support |
22 | | - details: All common platforms are natively supported, such as Windows, macOS and Linux, and third parties have already supported mobile platforms. |
| 11 | +- title: Multiple Entries and Exits |
| 12 | + details: A single V2Ray process can concurrently support multiple inbound and outbound protocols, each operating independently. |
| 13 | +- title: Customizable Routing |
| 14 | + details: Incoming traffic can be routed through different exits based on configuration. Easily implement traffic splitting by region or domain name to achieve optimal network performance. |
| 15 | +- title: Multi-Protocol Support |
| 16 | + details: V2Ray can enable multiple protocols simultaneously, including Socks, HTTP, Shadowsocks, Trojan, Vmess, VLESS, and more. Each protocol can be configured with its own transport layer, such as TCP, mKCP, QUIC, gRPC, and WebSocket. |
| 17 | +- title: Stealth and Security |
| 18 | + details: V2Ray nodes can masquerade as normal websites (HTTPS), blending their traffic with regular web traffic to avoid third-party interference, while providing packet obfuscation and replay protection features. |
| 19 | +- title: Load Balancing |
| 20 | + details: Incoming traffic is automatically distributed to the most suitable exit points using probing strategies and weighted algorithms. |
| 21 | +- title: Multi-Platform Support |
| 22 | + details: Native support for all common platforms including Windows, macOS, and Linux, with third-party support available for mobile platforms. |
23 | 23 | footer: Licensed under CC-BY-SA 4.0 | Copyleft 2015-Present V2Fly Community |
24 | 24 | --- |
25 | 25 |
|
26 | | -## Who will lead the development of Project V |
| 26 | +## Who Leads Project V Development? |
27 | 27 |
|
28 | | -We are a group of people who love freedom. We tend to remain anonymous and do not disclose any identifying information as much as possible. |
| 28 | +We are a group of freedom-loving individuals. We prefer to remain anonymous and disclose as little personal information as possible. |
29 | 29 |
|
30 | | -You can use GitHub, Telegram, Email [discuss with us](guide/help.md). |
| 30 | +You can [discuss with us](guide/help.md) through GitHub, Telegram, or Email. |
31 | 31 |
|
32 | | -## Contribution |
| 32 | +## Contributing |
33 | 33 |
|
34 | | -Welcome to contribute to the project! Even if you don't know how to write code, there are still many ways to help improve it. Here are some examples: |
| 34 | +We welcome your contributions to the project! Even if you don't know how to code, there are many ways you can help improve the project. Here are some examples: |
35 | 35 |
|
36 | | -- ⚙️ **Help develop V2Fly**! Clone the warehouse, check out the code, and submit a high-quality Pull request! |
| 36 | +- 🌐 **Translation**. Help translate V2Ray into more languages or improve the quality of existing translations. |
| 37 | +- 🐛 **Bug Reporting**. Report bugs or other issues encountered while using V2Ray by submitting an [issue](https://github.com/v2fly/v2ray-core) |
| 38 | +- ⚙️ **Help Develop V2Fly**! Clone the repository, check out the code, and submit high-quality Pull requests! |
37 | 39 | - 📆 **Community Maintenance** Help us create and maintain the V2Fly community! |
38 | | -- ...You can do more! |
39 | | -- ...If you have 2+ PRs, you can apply to join the V2Fly team! |
| 40 | +- ...and more! |
40 | 41 |
|
41 | | -## Authorization |
| 42 | +## Licensing |
42 | 43 |
|
43 | | -- Core uses MIT License |
44 | | -- The website ([v2fly.org](https://www.v2fly.org/)) is authorized under the [CC BY SA 4.0 International License Agreement](https://creativecommons.org/licenses/by-sa/4.0/deed.zh) . |
45 | | - * Including all visible text and pictures on the website. |
46 | | - * Include Project V icon files. |
| 44 | +- Core is licensed under the MIT License |
| 45 | +- The website ([v2fly.org](https://www.v2fly.org/)) is licensed under [CC BY SA 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/). |
| 46 | + * Including all visible text content and images on the website. |
| 47 | + * Including Project V icon files. |
47 | 48 | * Including the source code used to generate the website, namely [v2fly/v2fly-github-io](https://github.com/v2fly/v2fly-github-io). |
48 | | -- The copyright of the content created by a third party belongs to its creator. Project V waives ownership of this content. |
49 | | - * Including screenshots of Project V in use. |
50 | | - * Including the configuration files required to run Project V. |
51 | | - * Including the log files generated when Project V is running. |
| 49 | +- Content created by third parties remains the copyright of their respective creators. Project V waives all ownership of such content. |
| 50 | + * Including screenshots taken during the use of Project V. |
| 51 | + * Including configuration files required to run Project V. |
| 52 | + * Including log files generated during Project V operation. |
0 commit comments