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