When offering user support for Freenet, it would be helpful to have a plaintext node stats / diagnostic page available that the user could copy/paste into an email, pastebin, or similar.
The stats page on Freenet often has nonsensical values for the breakdown of how much bandwidth has been used for each different type of traffic. For example, negative bytes spent on overhead. The bytes used stats code needs a thorough audit and cleanup.
Currently, Freenet content is addressed by a mix of different techniques, depending on a variety of factors. Sometimes an http: URL is used, sometimes just the bare key. None of these options manages to be both consistently functional and standards compliant. Instead, Freenet should use compliant URIs of the form freenet:key. In order to function properly, this needs a certain amount of browser support, probably via a plugin.
URLs using % encoding for special characters are often handled very poorly. They should work just like other URLs.
As files on Freenet get old, they become unavailable if they aren't popular. Sometimes people will request that someone reinsert the file. This is currently slow, awkward, and more of a security risk than it could be. Some additional FCP primitives and FProxy interfaces would make writing good filesharing clients easier. Specifically, it should be easy to reinsert only a portion of an existing file, since that is usually all that is required. This would both be faster and more secure than reinserting the whole file. It should also be easy to make sure that you use the same settings as the original uploader, thus avoiding generating a new key.
If a Freenet node is running in gateway mode, it should serve a separate set of bookmarks to non-privileged users.
The Freenet network implements a content filter on downloads, in an attempt to remove some of the most obvious security holes. For example, including images from the WWW in a Freenet page compromises the reader's anonymity, in a way that would not be considered a security problem in most other contexts.
The problem is that this can make more complicated pages difficult to write, as there is no convenient way to test what the content filter will do to your document before uploading it.
See bug 3922 for details.
Library currently uses the ancient SnakeYaml library v. 1.5
I would like this plugin to be updated to use v. 1.10
Freenet plugins can currently be loaded or unloaded, but not disabled. This would offer a convenient way to not run a plugin but retain its configuration and such.
The Freenet Japanese localization is very incomplete and out of date.