How does this compare to i2pd, a more mature C++ implementation of I2P?
kovri is a rebrand of i2pd, someone took one of the worst revisions of i2pd back when it sucked more and called it kovri and to this very day still have loads of bugs that are fixed for over a year in i2pd. somehow the kovri people managed to make the code worse than it was when they started complexity wise.
disclosure: I work on i2pd a bit.
[1] - https://github.com/monero-project/kovri-docs/blob/master/i18...
there is an off-by-one that prevents the dht from working properly, it actively poisons the network. i fixed this in i2pd last year, the code changed so much I think that's where it is located now. there are a few more bugs like that i know of off the top of my head but i'd need more coffee. i got kicked off kovri for trying to fix bugs, good luck to them in the future. they're going to need a major management additude readjustment if they want to provide a proper functioning i2p router, so far all they have done is shoo away competent developers with the way they treat PR.
further updates:
kovri does not provide extra "security" or "quality" as seemingly none of the bugs I and many others fixed in i2pd have been fixed in kovri. that document is a huge load.
if anyone wants to contribute to i2pd see: https://github.com/purplei2p/i2pd/
https://github.com/PurpleI2P/i2pd/graphs/contributors
Where have you been between June and November 2015? Kovri was meant to be just an integration of i2pd into Monero, not a fork. But yeah... When the only maintainer of a project is gone for half a year, what do you expect? Anyone familiar with Git is able to see when anonimal finally forked away...
https://github.com/monero-project/kovri/graphs/contributors
But yeah, then you came back and started developing again after 6 months of nothing? Just don't be like an offended asshole and maybe try to cooperate or just let it go the open source way and the better solution will probably get the most adoption.