The zapret project, a tool designed to bypass Deep Packet Inspection (DPI) mechanisms, has seen minimal development progress over the last 30 days, with the focus primarily on bug fixes and documentation enhancements rather than new feature development.
The zapret project aims to help users circumvent internet censorship by employing various DPI evasion techniques. It is particularly targeted at regions with strict censorship laws, such as Russia.
Recent pull requests and issues indicate a focus on resolving technical debt and improving user documentation. PR #205 addresses compiler warnings and code cleanup, reflecting ongoing efforts to maintain code quality. Meanwhile, PR #217 and PR #142 highlight attempts to standardize documentation formats and expand setup guides for different platforms. However, compatibility issues persist, as seen in PR #257's discussion on FreeBSD support.
Summary
Quantified Reports
Detailed Reportsnfq/darkmagic.c, documentation updates, and enhancements to the tpws module.| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 14 | 10 | 119 | 13 | 1 |
| 30 Days | 79 | 47 | 481 | 77 | 1 |
| 90 Days | 85 | 51 | 529 | 83 | 1 |
| 1 Year | 115 | 83 | 824 | 113 | 1 |
| All Time | 243 | 209 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| bol-van |  |
1 | 0/0/0 | 64 | 107 | 2685 |
| [anp/hsw] |  |
1 | 1/0/0 | 10 | 16 | 122 |
| Vladimir Goncharov |  |
1 | 1/1/0 | 1 | 3 | 59 |
| Ivan |  |
1 | 1/1/0 | 1 | 1 | 24 |
| mdashlw |  |
1 | 1/1/0 | 1 | 1 | 2 |
| Ivan Grishaev |  |
1 | 1/1/0 | 1 | 1 | 2 |
| None (Lui22) | 0 | 0/1/0 | 0 | 0 | 0 | |
| s-s-s (s-s-s) | 0 | 2/0/2 | 0 | 0 | 0 | |
| None (UnkwUsr) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Max Makarov (maxpain) | 0 | 0/0/1 | 0 | 0 | 0 | |
| Nik (nikrays) | 0 | 1/0/1 | 0 | 0 | 0 | |
| None (rexa302) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Andrey Kiryanov (kiryanov) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Ignat Loskutov (loskutov) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Ilya Bogdanov (zeerayne) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Livia Medeiros (LiviaMedeiros) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Artem Klevtsov (artemklevtsov) | 0 | 1/0/1 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The GitHub repository for the zapret project has seen a significant amount of activity, with a total of 34 open issues. Recent discussions reveal ongoing challenges users face with various configurations, particularly concerning the effectiveness of the tool against different ISPs and protocols. Notably, issues related to YouTube access, DNS configurations, and the interaction between zapret and other network services have been prevalent.
Several issues exhibit common themes, such as difficulties in bypassing specific censorship measures imposed by ISPs like Ростелеком and МГТС. Users frequently report that while some websites are accessible, others remain blocked or experience significant latency. There is also a recurring mention of problems with QUIC protocol handling and the need for tailored configurations to achieve optimal performance.
Here are some of the most recently created and updated issues:
Issue #333: zapret.service autostart is not working
zapret.service does not start automatically after a system reboot, requiring manual intervention.Issue #332: Add z alias for zapret service
Issue #330: Socks5 на Windows
Issue #328: PFSense 2.7.2 HighLoad
Issue #325: Приложение YouTube для Android TV
Issue #323: Build nfq for Openwrt 14.07
This analysis highlights both the active engagement of users within the zapret community and the ongoing challenges they face in navigating internet censorship effectively.
The repository zapret has a total of 4 open pull requests and 39 closed pull requests, with recent activity focused on bug fixes, documentation improvements, and enhancements to functionality. The project continues to evolve with contributions addressing both technical issues and user experience.
PR #257: Do not setgroups() on FreeBSD
Created 18 days ago, this PR addresses a compatibility issue with FreeBSD where the setgroups() call fails, rendering certain options ineffective. The discussion highlights differences in behavior between FreeBSD and Linux, indicating the need for further testing.
PR #217: doc: change Russian readme extension to .md
Opened 24 days ago, this PR aims to standardize the documentation format by changing the Russian README file from .txt to .md. Review comments suggest that this change should have been part of a previous commit due to broken markdown formatting.
PR #205: fixing compiler warnings and code cleanup
This PR was created 26 days ago to address various compiler warnings and clean up the codebase. It discusses specific warnings related to type comparisons and suggests that some issues may be bugs that need fixing.
PR #142: Added docs for OPNsense
Created 472 days ago, this PR provides documentation for setting up zapret on OPNsense routers. Comments indicate that users have successfully implemented the changes but suggest further refinements are necessary.
PR #326: Fix get_antizapret_domains.sh URL
Closed 2 days ago without merging, this PR proposed a fix for a URL used in a script. The change was already made in the main branch before this PR was submitted.
PR #319: fix typo
Merged 6 days ago, this minor PR corrected a typo in the documentation.
PR #315: option to bind to specified address for outbound connection
Merged 6 days ago, this significant enhancement allows users to specify source addresses for outbound connections, improving flexibility for users with multiple IP addresses.
PR #303: Add .gitignore
Closed without merging after discussions clarified that the files intended for exclusion were already managed appropriately in the repository.
The current state of pull requests in the zapret repository reveals several themes and areas of focus among contributors.
A notable trend among recent pull requests is the emphasis on technical improvements and bug fixes. For instance, PR #205 focuses explicitly on addressing compiler warnings, which is critical for maintaining code quality and ensuring compatibility across different systems. The detailed discussions within this PR highlight a collaborative effort to understand and resolve complex issues related to type handling and compiler behavior. This indicates an active engagement from contributors who are not only interested in adding features but also in refining existing code.
Another significant theme is the ongoing effort to enhance documentation. PRs like #217 and #142 illustrate a commitment to improving user experience by ensuring that documentation is clear, accessible, and up-to-date. The transition from .txt to .md formats is particularly noteworthy as it aligns with modern practices in software documentation, making it easier for users to navigate and utilize the information provided. However, there are indications of some confusion regarding markdown formatting that need addressing, as noted in comments from reviewers.
The discussions surrounding PR #257 reveal ongoing challenges related to platform compatibility—specifically between FreeBSD and Linux. These types of issues are critical as they can significantly impact user experience depending on their operating environment. Contributors are actively engaging in discussions about these discrepancies, suggesting a healthy level of collaboration aimed at ensuring cross-platform functionality.
The number of closed pull requests (39) compared to open ones indicates a responsive community that actively reviews and integrates contributions. However, there are also instances where contributions were closed without merging due to redundancy or lack of necessity (e.g., PR #326). This reflects an efficient workflow but also highlights potential areas for improvement in communication about ongoing changes within the project.
While many contributions are constructive, there are anomalies such as PR #220 which was deemed "meaningless" by the repository maintainer. Such instances could indicate either miscommunication or a lack of clarity regarding contribution guidelines. Additionally, some pull requests appear focused on trivial changes (like typos), which while important for polish may not reflect substantial progress towards project goals.
In summary, the current landscape of pull requests in the zapret repository showcases an engaged community focused on enhancing functionality, improving documentation, and addressing compatibility issues while also navigating challenges related to contribution relevance and clarity. The project appears well-positioned for continued growth and refinement as it evolves in response to both user needs and technical requirements.
nfq/darkmagic.c, including a toolchain fix, handling of uninitialized fields, and header management.tpws module enhancements, including emergency connection closures, TCP user timeout options, and connection closing rewrites.bol-van, who is actively addressing both feature enhancements and bug fixes. This indicates a strong leadership role within the project.anphsw highlights an ongoing effort to improve code quality and maintainability.tpws, nfqws) indicate that the project is evolving with enhancements aimed at improving functionality and user experience.The development team is actively engaged in maintaining and enhancing the zapret project. The contributions are primarily led by bol-van, with support from other team members focusing on specific areas such as documentation and code quality. The collaborative nature of recent activities suggests a healthy development process, with ongoing efforts to address both user-facing features and underlying code stability.