3 - test bootstrapping via hostlist + transport/core/dht connect
7 - [#1585, #1583, #1582] transport-level disconnect (i.e. TCP) does not cause core-level
8 disconnect in a timely fashion (waits for connection timeout);
9 need to figure a way to make it near-instant in those cases
10 (i.e. rapid reduction in timeout on transport-level disconnect) [CG]
11 => may have been fixed with instant-notification of disconnect
12 to core on session-oriented connection hick-up; not perfect but
13 likely good enough until we get ATS going; still should be tested...
14 => "peers connected (transport)" now instantly goes to ZERO (core statistic),
15 but "established sessions" stays up...
16 * NAT/UPNP: [Milan / Ayush / MW]
17 - [#1609] code clean up
19 - integration with transport service:
21 + implement UDP, HTTP/HTTPS
23 - track paths content travels (PUT, reply-to-get) in messages,
24 pass to client (client API & protocol already support this!)
26 - implement multi-peer FS performance tests
30 - implement anonymity level > 1
32 - figure out where in the GUI we should show active upload operations and allow aborts
36 * Determine RC bugs and fix those (release should have no known real bugs)
40 - update books (especially for developers)
41 - make a NICE download page and figure out how to enable developers to publish TGZs nicely
44 - exclude content that will "soon" expire from migration
45 - make migration data rate & datastore IO-rate configurable
46 - exclude certain peers as targets (based on hash values) in each
47 iteration => same peer can only be picked every n-th iteration
48 for the same content => fewer duplicate sending!
50 * Determine RC bugs and fix those (release should have no known real bugs)
54 - WiFi transport backend [DB]
55 - Implement method of learning our external addresses from
56 other peers; need some kind of threshold-based
57 scheme, limiting both the total number of addresses that we accept
58 this way as well as requiring multiple confirmations; also, we
59 should possibly try to confirm that the given address works for
60 us ourselves (loopback-style) before adding it to the list
61 + we may be able to simplify WELCOME messages (no need to add
62 addresses there anymore, but may help to learn them there anyway...).
63 + we probably want some kind of voting/counting for learning IP addresses
64 (maybe including IP addresses in ads proportional to how often others
65 report them? we at least need some protection against >64k HELLOs!),
66 + provide a way to give the user a list of "learned" IP addresses and
67 a way to easily "veto" addresses off the list!
68 => If MiM attacker uses vetoed address, blacklist the specific IP for
69 the presumed neighbour!
70 - need to periodically probe latency/transport cost changes & possibly switch transport
72 - proper bandwidth allocation
75 - merge multiple HELLOs of the same peer in the transmission queue
76 (theoretically reduces overhead; bounds message queue size)
77 - merge multiple iteration requests over "all" peers in the queue
78 (theoretically reduces overhead; bounds messgae queue size)
80 - should use BIO instead of mmap
82 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
83 - use different queue prioritization for probe-downloads vs. normal downloads
84 - re-implement gnunet-auto-share
86 - allow limiting UNIX socket access by UID/GID
89 - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
90 - add progress dialog for 'add_dir_at_iter' scan (can take a while...)
91 - NS list in search dialog should use colors to offset our own namespaces from the others
92 - right-clicking on NS list in search dialog should open menu that allows
93 * viewing full meta data
94 * deletion of namespace info
95 - implement unindex operation (use dialog with all indexed files for selection)
96 - finish publish dialog details:
97 + normalize keywords (edit subdialog)
98 - implement download by URI dialog; figure out where to display those downloads!
100 - better tracking of which config changes actually need to cause process restarts by ARM.
101 - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
102 - discover dependencies between services
104 - better crash management (attach debugging support, capture and analyze
105 debug output, detect random vs. deterministic crashes)
106 - '-m EMAIL' option for alternative e-mail TO
107 - '-f FILENAME' option to write report to file instead of e-mail (for testing!)
111 - expire 'ancient' HELLOs (those without valid addresses AND that
112 we have not 'used' (for their public keys) in a while; need a way
113 to track actual 'use')
114 - make sue we also trigger notifications whenever HELLOs expire
116 - repeatedly resolve hostname and look up interfaces to determine our own IP
117 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
119 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
120 - WiFi transport backend
121 * nice signal strength adjustment [MW]
122 * energy cost in ATS [MW]
124 - testcase would be nice
125 - generic block support for DHT
127 - test notification-based statistics API
128 - implement statistics GUI (=> start from gnunet-gtk by button!)
130 - move peerinfo to new GUI (=> start from gnunet-gtk by button!)
131 - extend peer dialog with green-yellow-red connectivity status lights
132 - extend peer dialog with country flags and names
135 * SMTP transport backend:
136 - sending (SMTP/SMTPS)
137 - receiving (IMAP/IMAPS/POP?)
140 - resource limit integration with ATS
144 - integration with DHT routing
145 - optimized routes (beyond DHT/DV)