Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's going on there for Qv2ray/Qv2ray? #4

Open
rockyoung opened this issue Jul 2, 2021 · 11 comments
Open

What's going on there for Qv2ray/Qv2ray? #4

rockyoung opened this issue Jul 2, 2021 · 11 comments

Comments

@rockyoung
Copy link

Sorry for posting this question here couse I don't know where is the better place to ask about this, and I'm really curious about the statement of “Unlike Qv2ray/Qv2ray whose control has been forcibly taken away from the author by another organization owner.”

@database64128
Copy link
Contributor

database64128 commented Jul 2, 2021

On April 27, 2021, DuckSoft, co-owner and community leader of the Qv2ray organization, kicked U-v-U (a.k.a gcc), main developer of Qv2ray who contributed over 95% of the code, out of the organization, over a dispute about a change the main developer introduced to the project.

The change, which induces Qv2ray to crash when the configured backend is Xray and the backend crashes, was intended as a boycott by the main developer against the Xray developer rprx over rprx's toxic behavior and negative influence in the community.

DuckSoft, who voiced his objection to the change and was ignored by the main developer, proceeded to revert the change without notice. The main developer force pushed to remove the revert commit, and was removed from the organization by DuckSoft for doing so "irrationally".

Since then, the development of Qv2ray at the Qv2ray organization has stalled. At some point, DuckSoft also stopped showing up in the community. The main developer continues development in his personal fork, and will soon release the first preview version of Qv2ray 3.0.

@Nek0kawa1
Copy link

Nek0kawa1 commented Jul 4, 2021

The Soviet Union collapsed from inside.
GFW wins this round.

@rockyoung
Copy link
Author

Well, both sides seem to be a bit extreme...really sad about the situation :(

@SmartPolarBear
Copy link

Where can I find details about "Developer rprx's toxic behavior and negative influence in the community" ?

@ghost
Copy link

ghost commented Aug 23, 2021

Where can I find details about "Developer rprx's toxic behavior and negative influence in the community" ?

There is no mean to keep on this topic. Let's lookfoward to the future.

@database64128
Copy link
Contributor

@SmartPolarBear Despite his contributions to many projects and his expertise in censorship circumvention, rprx has always been a controversial figure in the community. His populist and nationalist approach has made him extremely popular among regular, mostly non-technical users, while being a narcissist frequently gets him into quarrels and disputes with other developers. Where there's rprx, there's chaos and division.

  • Look for issues with comments from rprx. (e.g. The infamous License issue XTLS/Go#9)
  • Look through the chat history in rprx's Project X Telegram group, where rprx sometimes posts his populist, nationalist and sexist opinions.
  • There are also many internal discussions where rprx shows little to no respect for others.

@Apihplays
Copy link

https://github.com/moodyhunter/QvPersonal error 404 , what happen nowadays ?

@database64128
Copy link
Contributor

@Apihplays The author doesn't like attention on his personal repo, and has decided to stop maintaining it. The code from that repo has been reinstated here and is released under the original name Qv2ray. Nightly builds and AUR package are also available for this repo.

@iandol
Copy link

iandol commented Aug 27, 2021

@database64128 — thank you for your information. Are you only intending to build for arch, or will you build appimage's or some other generic static package that would work on e.g. Debian-based systems?

@database64128
Copy link
Contributor

@iandol I'm currently not interested in maintaining anything outside the Arch ecosystem. If you're interested, feel free to do it. This project is open to contributions from everyone.

@iandol
Copy link

iandol commented Aug 27, 2021

Thank you, I personally don't have the expertise to make a useful contribution, and I'm just grateful for all those who are keeping this project alive in whatever form it may be!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants