3 - perf_gnunet_service_fs_p2p_trust causes fs service to segfault
4 - download of 100 MB file from 'leach' peer hung due to
5 failure of core-api to call back after a change preference request
6 (structs indicate request was transmitted but reply never received?)
8 - test_gnunet_service_fs_p2p:
9 => sometimes DATASTORE get operation fails to queue on target (why?)
10 => do we need to just make the queue larger?
11 - with core queue size of 1, we get notify_transmit_ready
12 from core API returning NULL (why? ok? just have larger queue?)
13 - other runs (-L DEBUG) with downloads using the new 'trust' test show
14 non-deterministic results (for any set of peers)
15 - implement 'SUPPORT_DELAYS'
19 - write chapter on DHT/block [Nate]
20 - make a NICE download page
22 - UDP fragmentation [MW]
24 - [#1609] code clean up
26 - integration with transport service:
28 + implement UDP, HTTP/HTTPS
30 - figure out where in the GUI we should show active upload operations and allow aborts
35 - consider re-issue GSF_dht_lookup_ after non-DHT reply received
36 - implement multi-peer FS performance tests + gauger them!
41 * Determine RC bugs and fix those (release should have no known real bugs)
45 - 'TransmitFunction' requires plugins to have "unbounded" queue (or at least
46 queue of size > 2), might be better to have at MOST one message pending
47 per plugin/target and only send the next one after the continuation was
48 called (or use 'notify_transmit_ready-style API?)
49 - WiFi transport backend [DB]
50 - Implement method of learning our external addresses from
51 other peers; need some kind of threshold-based
52 scheme, limiting both the total number of addresses that we accept
53 this way as well as requiring multiple confirmations; also, we
54 should possibly try to confirm that the given address works for
55 us ourselves (loopback-style) before adding it to the list
56 + we may be able to simplify WELCOME messages (no need to add
57 addresses there anymore, but may help to learn them there anyway...).
58 + we probably want some kind of voting/counting for learning IP addresses
59 (maybe including IP addresses in ads proportional to how often others
60 report them? we at least need some protection against >64k HELLOs!),
61 + provide a way to give the user a list of "learned" IP addresses and
62 a way to easily "veto" addresses off the list!
63 => If MiM attacker uses vetoed address, blacklist the specific IP for
64 the presumed neighbour!
65 - need to periodically probe latency/transport cost changes & possibly switch transport
67 - check indexes / SQL for performance
69 - proper bandwidth allocation
72 - merge multiple HELLOs of the same peer in the transmission queue
73 (theoretically reduces overhead; bounds message queue size)
74 - merge multiple iteration requests over "all" peers in the queue
75 (theoretically reduces overhead; bounds messgae queue size)
77 - should use BIO instead of mmap
79 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
80 - use different queue prioritization for probe-downloads vs. normal downloads
81 - re-implement gnunet-auto-share
82 - implement 'GNUNET_FS_file_information_create_from_directory', avoiding
83 code duplication with gnunet-gtk's similar code (!)
86 - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
87 - add progress dialog for 'add_dir_at_iter' scan (can take a while...)
88 - NS list in search dialog should use colors to offset our own namespaces from the others
89 - right-clicking on NS list in search dialog should open menu that allows
90 * viewing full meta data
91 * deletion of namespace info
92 - implement unindex operation (use dialog with all indexed files for selection)
93 - finish publish dialog details:
94 + normalize keywords (edit subdialog)
95 - implement download by URI dialog; figure out where to display those downloads!
96 - add combo box to select desired mime type for search
98 - better tracking of which config changes actually need to cause process restarts by ARM.
99 - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
100 - discover dependencies between services
102 - better crash management (attach debugging support, capture and analyze
103 debug output, detect random vs. deterministic crashes)
104 - '-m EMAIL' option for alternative e-mail TO
105 - '-f FILENAME' option to write report to file instead of e-mail (for testing!)
109 - expire 'ancient' HELLOs (those without valid addresses AND that
110 we have not 'used' (for their public keys) in a while; need a way
111 to track actual 'use')
112 - make sue we also trigger notifications whenever HELLOs expire
114 - repeatedly resolve hostname and look up interfaces to determine our own IP
115 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
117 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
118 - WiFi transport backend
119 * nice signal strength adjustment [MW]
120 * energy cost in ATS [MW]
122 - testcase would be nice
124 - implement statistics GUI (=> start from gnunet-gtk by button!)
126 - move peerinfo to new GUI (=> start from gnunet-gtk by button!)
127 - extend peer dialog with green-yellow-red connectivity status lights
128 - extend peer dialog with country flags and names
131 * SMTP transport backend:
132 - sending (SMTP/SMTPS)
133 - receiving (IMAP/IMAPS/POP?)
136 - resource limit integration with ATS
142 - optimized routes (beyond DHT/DV)