3 - Migration test error scenarios:
4 * client fails to connect to FS service for download (requests never make it to FS)
5 FS was running initially, but is shut down around the time the source peer (!)
6 is supposed to die; the OTHER FS service (the one that was supposed to die) is still up!
7 - TTL/priority calculations
8 - hot-path routing, load considerations
9 - active reply route caching design & implementation of service; gap extension!
13 - write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
14 - implement DV service
15 - implement DV library (looks done)
16 - implement DV transport plugin
18 - implement performance tests (needs tbench)
20 - needs more testing (especially F2F topology) & transport blacklisting
22 - only connect() sockets that are ready (select()) [Nils]
23 [On W32, we need to select after calling socket before doing connect etc.]
24 - add support for UNIX domain sockets [CG]
29 / metadata view update
33 - double-clicking on search result in master list should open save-as dialog for CHK/LOC URIs
34 - right-clicking on search result should open menu that allows:
35 + viewing full meta data
37 + starting recursive download
38 + aborting active download
39 - implement publish dialog
41 + edit (meta data add, meta data del, meta data type population, keyword add (button, activate entry line),
42 keyword remove, anonymity level, priority, index/insert, normalize keywords,
43 previews, preview widget for file chooser!?)
44 + mark 'insert file' button inconsistent for directories
50 + open (import directory structure)
53 - pick appropriate sort-by columns for various tree view columns
57 - transport-level disconnect (i.e. TCP) does not cause core-level
58 disconnect in a timely fashion (waits for connection timeout);
59 need to figure a way to make it near-instant in those cases
60 (i.e. rapid reduction in timeout on transport-level disconnect)
61 - encrypted P2P transmission (loopback) tops at 2 MB/s on my quad-core;
62 why is it so slow? Fix! (see core_api_reliability test)
64 - good to have for transport/DV evaluation!
66 - implement DHT service
68 - implement performance tests
70 - better crash management (attach debugging support, capture and analyze
71 debug output, detect random vs. deterministic crashes)
72 - discover dependencies between services
73 => need UNIX domain sockets first!
74 - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
76 - datastore reservation (publishing)
77 - location URIs (publish, search, download)
78 - unindex on index failure
79 - utilize in-line files in meta data always (including in search results or
80 when download is triggered manually and for probes); currently the data is
81 only used when users do a general 'recursive' download
82 - non-anonymous FS service (needs DHT)
83 + DHT integration for search
84 + CS-DHT-functions (DHT-put of LOC)
85 + P2P-functions (DHT-get)
86 - listing of learned namespaces
87 - collection API & tests
88 + gnunet-pseudonym (collection support)
89 - implement FS performance tests
95 - implement open directory dialog
96 - implement new-pseudonym dialog
98 - NS list in search dialog should use colors to offset our own namespaces from the others
99 - double-clicking on NS list in search dialog should move 'root' to keyword line
100 - right-clicking on NS list in search dialog should open menu that allows
101 + viewing full meta data
102 + deletion of namespace info
103 - implement API to get notifications about bandwidth assignments to individual peers
104 - implement API to get notifications about updates to liveness of individual peers (before disconnect)
105 - extend peer dialog with green-yellow-red connectivity status lights
106 - implement statistics tabs
107 - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
108 - implement unindex operation (use dialog with all indexed files for selection)
109 - implement download by URI dialog; figure out where to display those downloads!
110 - figure out where in the GUI we should show active uploads/unindex operations and allow aborts
112 - design & implement new setup tool
116 - good to have for DV/DHT evaluation!
117 * Determine RC bugs and fix those!
119 - GNUNET_DATASTORE_cancel method not tested
121 - modify configuration to allow controlling connections for non-local starts
122 - testbed creation with topology (needs working F2F topology)
124 - implement testcases for distributed testing
125 - test basic peer re-configure
126 - test topology creation
127 - test churn generation
128 - consider changing API for peer-group termination to
129 call continuation when done
131 - finalize API design
134 - integration with transport service
135 * MYSQL database backends: [CG]
139 - reconstruct IBLOCKS from DBLOCKS if possible (during download; see FIXME in fs_download)
140 - add support for pushing "already seen" search results to FS service for bloomfilter (can wait)
141 - use different 'priority' for probe downloads vs. normal downloads
143 - better tracking of which config changes actually need to cause process restarts by ARM.
147 - expand bibliography
148 - convert documentation pages to books
149 - update books (especially for developers)
150 - create good Drupal theme for GNUnet
151 - make a NICE download page and figure out how to enable developers to publish TGZs nicely
152 - port "contact" page
153 - add content type for "todo" items?
154 * POSTGRES database backends: [CG]
157 * Determine RC bugs and fix those!
161 - SMTP transport backend
162 - HTTPS transport backend
163 + improved HTTPS support in MHD
165 - Implement method of learning our external addresses from
166 other peers; need some kind of threshold-based
167 scheme, limiting both the total number of addresses that we accept
168 this way as well as requiring multiple confirmations; also, we
169 should possibly try to confirm that the given address works for
170 us ourselves (loopback-style) before adding it to the list
171 + we may be able to simplify WELCOME messages (no need to add
172 addresses there anymore, but may help to learn them there anyway...).
173 + we probably want some kind of voting/counting for learning IP addresses
174 (maybe including IP addresses in ads proportional to how often others
175 report them? we at least need some protection against >64k HELLOs!),
176 + provide a way to give the user a list of "learned" IP addresses and
177 a way to easily "veto" addresses off the list!
178 => If MiM attacker uses vetoed address, blacklist the specific IP for
179 the presumed neighbour!
180 - implement gnunet-transport (transport configurator / tester)
181 - UPnP-based IP detection
182 (Note: build library always, build service when libxml2/etc. are available)
184 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
186 - expire 'ancient' HELLOs (those without valid addresses AND that
187 we have not 'used' (for their public keys) in a while; need a way
188 to track actual 'use')
189 - make sue we also trigger notifications whenever HELLOs expire
196 - should use hash map to look up sessions
198 - should use BIO instead of mmap
200 - need to periodically probe latency/transport cost changes & possibly switch transport
201 - should use hash map to look up Neighbours (service AND plugins!)
203 - check for duplicates on insertion (currently, same content is frequently
204 stored again [seen with KBLOCKS and SBLOCKS]!)
206 - merge multiple HELLOs of the same peer in the transmission queue
207 (theoretically reduces overhead; bounds message queue size)
208 - merge multiple iteration requests over "all" peers in the queue
209 (theoretically reduces overhead; bounds messgae queue size)
211 - use different queue prioritization for probe-downloads vs. normal downloads (!?)
215 - repeatedly resolve hostname and look up interfaces to determine our own IP
216 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
218 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
220 - testcase would be nice...