Suggestions

From Freenet Wiki

Put your suggestions here.

Uservoice

Until recently we were using UserVoice[1] to track user suggestions and their respective popularities. Unfortunately the free version of UserVoice does not provide any adequate tools to deal with spam - in particular it is not possible to remove a spamming user.

The most popular ideas on uservoice were:

• Write a killer filesharing application - See Filesharing. Currently Freenet has poor file searching and poor data persistence.
• One GUI for all - This was originally a plea for a dedicated browser for Freenet, but IMHO the main issue is getting more functionality into the web interface and avoiding any clunkiness caused by its being a web interface. See Freetalk and FlogHelper.
• Add a 'pause' feature - This has been planned for a while, the most important issue from the comments appears to be getting the node back up to speed quickly after a pause.
• Implement reinsert on demand - This is closely related to Filesharing and data persistence.
• Use the port 80,443,53,1863 for comunication - This seems to be about transport plugins: Many people can't use Freenet because they can't use encrypted UDP, they may only be able to use TCP or even HTTP.
• Make FMS/Freetalk part of the Freenet project A working messaging system (FMS/Freetalk) could be included in the core Freenet project and some fraction of time could be dedicated to it.

Currently the lack of a working, trusted, bundled messaging system contrasts with good usability of core Freenet. This is an issue for end users and harms user retention, because communities cannot exist without messaging. (Some people stopped running Freenet node altogether since Frost is unavailable).

The proposal is: - As a minimum, Freenet devs could review FMS/Freenet specs and publish an official "RFC-like" specifications for Freenet messaging. This would settle disputes over minor details. Making trusted specifications is of utmost importance too, because several messaging standards failed in the past (FMB, Frost) and both developers and users mistrust any new standard assuming it is fundamentally flawed too.

- Ideally, Matthew could spend some time (say ~3 months) working on the messaging system. This could be a good alternative to the (proposed) diversion of donations to other projects. I am sure that most people would appreciate the trade-off: getting a working messaging system, even if core Freenet schedule is delayed few months.

Any suggestions for alternatives to uservoice would be very helpful. Please add them here. The obvious thing is a bug tracker with a voting system, but our current bug tracker[2] is rather intimidating and unfriendly.