I've been thinking of a tree-based representation, but it wouldn't be the default. Reason is, the JTree structure is much slower than JTable and if there are many shared files (as in tens of thousands) the gui would get very slow. I will add it at some point though.


As far as MW is concerned nobody is firewalled, because you can reach any MW node regardless of their physical firewall-ness status. But for i2p, if you are firewalled you will participate much less in the network and hence get much less cover traffic, which is worse for anonymity. So it's a good thing to not be firewalled.


The I2P router uses UDP when available (the number of "SSU" connections are actually UDP connections to other I2P nodes). As usual, UDP is slightly faster and lower overhead than TCP.


Agreed that having this ability is important, but it requires me to write native code and I'm not particularly good at that. Nevertheless I hope to get to it at some point.


Checking is outsourced to the I2P router which checks shortly after startup and then on average every 13 minutes.



This setting is relevant only if "allow only trusted connections" is enabled. What happens is that if you allow only trusted connections, MW will only connect to those whom you have marked as "TRUSTED". In order to prevent your queries reaching untrusted nodes, in trusted mode queries travel one fewer hop. The "extra hop" setting overrides this behavior. See this GitHub ticket for a discussion on the issue https://github.com/zlatinb/muwire/issues/6


At the moment no id3 tags or other metadata (like comments) is used when searching, and it's not trivial to do so. Sure, I can copy/paste the id3 parsing from LW, but the underlying plumbing requires some more in-depth changes and design decisions.