docs: feasibility study for official SagerNet/sing-box switch#16
Conversation
Read-only investigation. Conclusion: not a drop-in switch. The core is starifly/sing-box (fork of MatsuriDayo/sing-box -> official). libcore imports Matsuri-only packages (nekoutils, protocol/shadowsocksr, protocol/snell) absent from official v1.13.x, and the app exposes SSR/Snell/Juicity as first-class types plus a 4830-line options schema mirroring the fork. Switching means re-platforming (weeks, high regression risk, loses protocols). Documents the breakage and the lower-risk alternatives (wait for starifly rebase, or backport specific features).
|
Warning Review limit reached
More reviews will be available in 5 hours, 50 minutes, and 30 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
Docs-only. Read-only investigation of switching the core from starifly/sing-box to official SagerNet/sing-box (requested).
Conclusion: NOT a drop-in switch. Findings:
Recommendation: keep the starifly core; for newer upstream features, wait for starifly/Matsuri to rebase onto newer official, or backport specific features. Full re-platform is a separate product decision.
No functional app changes.