4 ms·
>but it will pay big dividends later if I need to rewrite parts of the I2P backend. I'm all for clojure, open source, innovation and forking. But i urge you to
by fosap 14y ago
>but it will pay big dividends later if I need to rewrite parts of the I2P backend.
I'm all for clojure, open source, innovation and forking. But i urge you to stay part of i2p and not create incompatible releases. Maintaining your private branch will result in a lot of extra work, and I'm 100% sure that this will result unfixed security holes. The i2p project on the other hand would probably gladly accept your java patches.
- gw 14y agoUnderstood; I actually was moreso referring to rewriting I2PSnark, not I2P itself. The BitTorrent codebase is pretty old and I know I can improve it if I had time. I agree that touching the core/router code itself is dicey, but keep in mind the I2P developers themselves have encouraged people to make alternative implementations. I don't plan on that right now, though.
- robert_foss 14y agoI think the I2P community would be thrilled about I2PSnark patches. I2PSnark is in active development currently, as the I2P update mechanism is being moved into I2PSnark.