4 ms·

> 10,000+ lines of Go - Production-quality codebase It's definitely not "production-quality", in fact it seems AI generated. https://github.com/Jery0843/TorFo

by KomoD 10mo ago

> 10,000+ lines of Go - Production-quality codebase It's definitely not "production-quality", in fact it seems AI generated. https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456c1eb6893dd52dd024599cf/internal/api/server.go#L357 https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456... This isn't a websocket, it's SSE. Also lol: "// Simplified - in production use gorilla/websocket" https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456c1eb6893dd52dd024599cf/cmd/torforge/main.go#L753 https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456... "Test" functions that do nothing. https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456c1eb6893dd52dd024599cf/internal/ai/circuit_selector.go#L231 https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456... "in production would be more sophisticated" - but this was supposed to be "production-quality"? https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456c1eb6893dd52dd024599cf/internal/bridge/discovery.go#L389 https://github.com/Jery0843/TorForge/blob/42ffdb75da28c40456... Ignoring errors (also in so many other places)

0xjerry 10mo ago
Used AI to document the code for readability (it's OSS). The iptables rules, Kyber integration, and SOCKS handling are the actual work. Find me an AI that can set up transparent proxying with netfilter that doesn't leak. Fixed the sloppy comments though, thanks. Fair point on the error handling. Many of those are in non-critical paths (flag parsing, optional config loading), but you're right that they should be handled properly.