| Task | condorcet Benham | least contested (mean/std) | mean | median | cost estimate (mean personweeks) |
| Web of Trust: Finish first iteration of most critical speed fixes (1 bugtracker entry). Was subject of previous 2 years of paid work. Ensures this work is not left unfinished. Needed for Sone / Freetalk / filesharing / … (see all other sections except Technical Debt) | 2 | 37 | 0 | 3 | 2.833 |
| Darknet invitation bundles: Feature for adding a single use node reference to an installer executable. People could hand out the installer executable to their friends to allow them to connect by Darknet instantly. | 3 | 17 | 1 | 4 | 0.75 |
| Friend requests, like in Facebook: With primitive FOAF, both peers would still have to add each other. With friend requests, peers of your peers could just request to connect to you. Could use similar UI to Facebook friend requests. | 0 | 3 | 2 | 0 | 0.75 |
| Single use node references with authentication token: Currently, two users need to add the node reference of each other to create a connection. With this, only one of the two would have to add the other. Might benefit from FOAF (see 3 tasks below) for connectivity if Opennet is off. | 1 | 2 | 3 | 1 | 1.333 |
| Friend-of-a-friend connection suggestions ("FOAF"): Like the Facebook friend finder, Freenet could be improved to tell you about Darknet peers of your peers. You could then chose to add them as your peers. Part of the code exists. | 4 | 1 | 4 | 2 | 1.5 |
| Fred: Migrate to the Gradle build tool - Gradle can provide dependency fetching and verification support and then defer to the existing ant build. (Or we can move the project to fit standard directory structure and then the Gradle build becomes a lot easier to write.) | 12 | 4 | 5 | 5 | 0.5 |
| Short node references: Currently, references fill almost half a sheet of paper. Improve this by uploading node references to Freenet itself as a random KSK, with for example 128 bit entropy to be ~ 25 letters. (Requires having peers already, but without the UI could just show the long one) | 7 | 14 | 6 | 7 | 0.666 |
| Better feedback on progress: currently in FProxy progress is displayed in terms of completed blocks. Information on how many fetch / insert requests are running for each one, and the progress on them, could help make the default mode of operation seem like hanging. | 13 | 44 | 7 | 24 | 0.75 |
| Fundraising: While volunteers did help with fundraising, they don't seem to enjoy it very much – we've contacted much fewer entities than those listed in the Wiki. So also have Freenet's employee do it. Important as Matthew will require much higher level of funding to come back. | 6 | 20 | 8 | 16 | 8.0 |
| Language: Document how Freenet works, with a infographic, on the Wiki, detailing the remainder of speciality words. | 17 | 6 | 9 | 8 | 1.5 |
| Darknet chat improvements: Freenet allows sending messages to Darknet peers. The UI for that is very primitive. It could be improved, for example to be similar to Facebook chat. Needs fixes for high message loss probability. | 19 | 0 | 10 | 6 | 1.666 |
| New keytype: RSK (revocable) | 9 | 25 | 11 | 10 | 1.333 |
| Blogging (FlogHelper, not enabled by default due to WoT performance issues) | 14 | 30 | 12 | 20 | 1.333 |
| Fix lack of plugin data encryption: WoT, Freetalk, and potentially other plugins do not encrypt their databases when the user has configured Freenet to encrypt user data. Should be changed to obtain an encryption key from Freenet to encrypt their stuff. | 10 | 13 | 13 | 11 | 1.0 |
| Improve FProxy CSS3 support to allow better Freesite UI | 16 | 33 | 14 | 22 | 1.666 |
| Keepalive: This is very popular on uservoice. It could be improved significantly with some integration into the web interface and minor backend changes. | 24 | 8 | 15 | 9 | 1.666 |
| Update FSNG: Use a modern Windows installation with the default theme for screenshots | 5 | 35 | 16 | 56 | 0.5 |
| Language: Lower threshold of entry by working on how to install Freenet | 8 | 24 | 17 | 17 | 0.833 |
| Fred: does it provide sufficient benefits to re-add native acceleration for FEC, or crypto? Especially JVMs without gmp acceleration - Oracle on Windows. | 31 | 45 | 18 | 72 | 1.25 |
| Language: Simplify website language. Boil this into this for all pages. | 15 | 12 | 19 | 13 | 0.833 |
| Something like Icicle to ease setting up Darknet connections - perhaps add support for connecting nodes over text message or Signal? | 18 | 5 | 20 | 15 | 2.5 |
| Legal docs: Instead of the above suggestions, just link the Tor legal FAQ. Tor is pretty similar and thus we shouldn't need to create our own one. Notice especially that there are 200 countries in the world and 200 lawyers would be pretty expensive. | 11 | 46 | 21 | 35 | 0.5 |
| Website redesign: New CSS redesign | 21 | 9 | 22 | 14 | 1.5 |
| Fix plugin data leak: None of our official plugins deletes its database when the user uninstalls it. They also do not obey the "PANIC" button of Freenet which should delete all client data. | 32 | 7 | 23 | 12 | 1.0 |
| Language: Add these strings for install to translation resource. Bonus for looking at this. | 39 | 10 | 24 | 18 | 0.833 |
| Language: Fix current low-hanging problems with UI language, as per issues on transifex. | 38 | 21 | 25 | 26 | 0.833 |
| ‘How to’ YouTube video series: A couple of (maximal)-5-minute videos, each explaining one important practical aspect of using Freenet. Do this because currently we demand users to read far too much (FAQ, wiki, etc.). Example of ZeroNet. | 23 | 16 | 26 | 21 | 1.666 |
| Freetalk: Make Freetalk usable again by using the new WoT event-notifications API to fix its most severe performance issues. The API had been implemented as previous paid work to specifically allow repairing Freetalk. Thus we'd reap what we sowed there. | 27 | 42 | 27 | 30 | 10.66 |
| Language: Establish overview of, and do away with needlessly difficult words | 22 | 11 | 28 | 19 | 1.5 |
| Do not reject Freemail messages when an ID is not known, queue them for a period and attempt to find the identity | 40 | 23 | 29 | 23 | 0.833 |
| Add FCP calls to Freemail to setup a user and to change user passwords | 44 | 50 | 30 | 51 | 0.5 |
| Filesharing (#1 request on uservoice with 700 votes, not yet implemented but could easily be built upon Freetalk) | 28 | 48 | 31 | 39 | 12.0 |
| Website redesign: Migration to static Github Pages | 20 | 32 | 32 | 28 | 1.166 |
| Distributed version control (various tools for Git / Mercurial over Freenet, not finished yet and lack code review) | 42 | 38 | 33 | 53 | 1.666 |
| Website redesign | 25 | 22 | 34 | 25 | 6.0 |
| Social networking (Sone, not enabled by default due to WoT performance issues and issues of its own) | 26 | 29 | 35 | 29 | 6.0 |
| Forums (Freetalk, not enabled by default due to WoT performance issues and issues of its own: Freetalk itself needs its performance fixes in the “Speed” section. Also it needs general usability / security / bugfixing / polishing work which this entry shall be about.) | 45 | 49 | 36 | 40 | 13.33 |
| Add simple tunnels. The easiest approach here may be to have some automatically added temporary time limited or data throughput limited FOAF connections that form simple tunnels. Tunnels should have a probability to use for high HTL inserts and requests based on security settings for the node. | 37 | 40 | 37 | 33 | 12.0 |
| Update FSNG: Show web interface usage rather than Thunderbird to match modern user expectations | 41 | 53 | 38 | 57 | 0.75 |
| Legal docs: Sample response letters for the potential arrests or raids, especially for the recent events as some users were completely innocent. We need to educate LEA, more than ever, that it in itself is not a crime nor suspicious to run Freenet. | 34 | 15 | 39 | 27 | 2.25 |
| FLIP or FLIRCP could use work to become official plugins, maybe with a webclient instead of having to install a potentially privacy leaking 3rd party one. [Likely requires the WoT performance work in the “Speed” section.] | 36 | 19 | 40 | 31 | 3.5 |
| FlogHelper (WoT-based blogging app): Accumulate flogs of other users. List them nicely. Add a search function. Use that to replace or amend the current concept of FProxy's default bookmarks as entry point for Freenet. Hundreds of blogs instead of ~10 bookmarks. | 33 | 28 | 41 | 32 | 6.666 |
| Mail (Freemail, not enabled by default due to WoT performance issue) | 43 | 34 | 42 | 54 | 2.333 |
| Website redesign: Migration of more detailed documentation to Github Wiki, allowing website to focus on onboarding new users [Notice: we have 3 non-Github Wikis currently, 2 of those have already been waiting for migration into the main one for years.] | 29 | 26 | 43 | 37 | 3.0 |
| Legal docs: Have resources akin to the Tor legal FAQ for exit node operators, created by a legal expert on the official project page, that can be shown to LEA or users. Explain what it is used for, how to use it safely, best practices, plausible deniability, legal status, etc. | 35 | 27 | 44 | 34 | 8.0 |
| WoT: Second iteration of less critical performance fixes: Identity garbage collection: Stats show that less than 1000 of the 14000 WoT identities are still active (thanks to ArneBab). Thus, we need to GC abandoned identities. | 47 | 39 | 45 | 38 | 33.66 |
| New keytype: PSK (programmable subkeys - shared ownership) | 30 | 31 | 46 | 36 | 10.66 |
| WoT: Second iteration of less critical performance fixes: Reduce transaction size from O(512) to O(1): Split up "import trustlist" transaction into 1 transaction for each trust. | 48 | 47 | 47 | 42 | 33.66 |
| Warn users not to use Chrome, but instead an open source/free software browser | 55 | 52 | 48 | 63 | 0.5 |
| Transport plugins are a very popular feature request. There is code but it needs a lot of work, and it may be better to start from scratch. In any case it will involve breaking up a lot of monster classes (good for code quality), and a lot of knock-on effects on concurrency (less good!). | 46 | 18 | 49 | 41 | 18.66 |
| Alternate task instead of the above tests/doc: Permanently use 1 day per workweek (= 20% of total time) to deal with any kind of technical debt whatsoever. Allow the developer to chose freely which issues to deal with so even unimportant technical debt will be dealt with eventually. | 54 | 36 | 50 | 46 | 100 |
| Fix the installers (windows first, then packages for linux) | 63 | 51 | 51 | 50 | 100 |
| WoT: Second iteration of less critical performance fixes: Process results of peer review of xor’s Web of Trust bachelor’s thesis (which was about last year’s performance improvements). | 49 | 41 | 52 | 43 | 96.0 |
| Make robust search functionality part of the default installation [task is possibly not specific enough: Complexity depends a lot on search target: Freesites? FlogHelper flogs? Freetalk messages? WoT identities? Sones? Filesharing?] | 50 | 43 | 53 | 47 | 38.66 |
| fred: Documentation is said to be poor. Improve it. Would help people other than Matthew to understand the code. Good to do this now while Matthew is still available as a volunteer and we can thus maybe ask him questions. | 52 | 54 | 54 | 44 | 50.0 |
| Improve Shoeshop/blob handling [how?] | 57 | 55 | 55 | 45 | 32.66 |
| Freenet key links directed to a dedicated Freenet browser, opennet [= non-Freenet Internet?] links to the system default like in the AutoHotKey script "Freenet Browser Director” | 56 | 56 | 56 | 64 | 10.66 |
| Improve the vulnerability and functionality of Flip [One anonymous user commented that you may as well re-invent FLIP] | 58 | 57 | 57 | 67 | 34.0 |
| fred unit test coverage is 20%. Improve it. Would help people other than Matthew to understand the code. Good to do this now while Matthew is still available as a volunteer and we can thus maybe ask him questions. | 53 | 58 | 58 | 49 | 50.0 |
| Add ability to comment on Freesites (fulfilled by babcom (is opt-in) / Freetalk / Sone?) | 61 | 59 | 59 | 69 | 33.66 |
| WoT unit test coverage is 45%. Given the lower total line count, it would be possible to complete it to 100%. That would be a preparation of the major “refactoring” of replacing db4o with a different database. May become necessary: db4o’s vendor has abandoned it. | 51 | 60 | 60 | 48 | 35.33 |
| Frost-alike communication system supporting easy usability, encrypted and read-only boards and hidden instant messaging between 2 or more ID's, integrated file transfer agent, mixed bulletproof ID'd and unsigned messaging. [= e.g. Freetalk. Likely requires the WoT speed tasks.] | 62 | 61 | 61 | 68 | 42.66 |
| Document the content filter | 60 | 62 | 62 | 66 | 32.83 |
| Language: Add Transifex issues to main bugtracker | 59 | 63 | 63 | 58 | 32.83 |
| Alternate task instead of the above technical debt day: 1 day/week as “do whatever you want to”-day like Google does. Example activities: Generic education (new Java language features, programming patterns, algorithms, papers); Wiki; Drafting new apps; Tests; Doc; Mailing lists | 64 | 64 | 64 | 60 | 100 |
| Make dynamic web pages possible [likely bogus suggestion: We must not allow full JavaScript for the security issue of preventing tracking / de-anonymization. We usually use plugins instead such as Sone, FlogHelper, Freetalk, Freemail, etc. So you might vote for those above instead] | 67 | 65 | 65 | 52 | 48.0 |
| New core features - Enable using Freenet for new kinds of tasks/usecases | None | 66 | 66 | 55 | 100 |
| Outreach - Stuff that will help attract users, developers, and donors to Freenet | None | 67 | 67 | 59 | 100 |
| Technical debt - Stuff that will make future development faster | None | 68 | 68 | 61 | 100 |
| Security - Make Freenet more secure against attacks | None | 69 | 69 | 62 | 100 |
| p2p file exchange by time-set expiring keys [Imprecise task? Also violates main goal of Freenet of preventing censorship!?] | 65 | 70 | 70 | 65 | 36.0 |
| Maybe FLIRCP can add darknet N2NTMs as a backend? | 66 | 71 | 71 | 70 | 2.333 |
| User Experience - make things easier and more enjoyable to use | None | 72 | 72 | 71 | 100 |
| Speed - Improve performance of Freenet or Freenet applications | None | 73 | 73 | 73 | 100 |
| The goal of this stage of the funding allocation procedure is to estimate "value" of individual tasks. Value shall measure how useful each task would be to our users, to developers, to health of the project, etc. Every participant gets 1000 units of value to allocate between the tasks, starting from an equal distribution of units. So the only thing you should edit is to allocate those 1000 units in the "Value" column of each task. Everything else will be computed automatically. LibreOffice / OpenOffice can highlight the cells you should fill in: Go to "View" and select "Value highlighting" (CTRL+F8). The tasks are grouped into different areas such as "Speed" and "User experience" to ensure we think about all areas. Some tasks might be helpful to not only one but multiple areas. Nevertheless, they are only enlisted in one area. Thus you do not need to feel obliged to cast votes in every area, you might as well instead vote for the tasks which cover more than just the area they are enlisted at. When deciding about the value of a task, you might want to consider how many areas you think it covers. A few important things here to ensure we get the true benefit of "wisdom of the crowd": - Don't be strategic (e.g. don't over-allocate to one area because you assume others might under-allocate to it). - Don't collude. - Don't consider development cost in your value allocation, this will be done in the next stage. - If you aren't sure, leave stuff at an even allocation, don't assign 0 value. Once everyone has allocated, we will take the average for each task to be our group estimate for that task. | None | 74 | 74 | 74 | 100 |
| Instructions | None | 75 | 75 | 75 | 100 |
| None | 76 | 76 | 76 | 100 | |
| Remaining | None | 77 | 77 | 77 | 100 |
| Task category / Task | None | 78 | 78 | 78 | 100 |