3 - Migration test error scenarios:
4 1) peers fail to connect (very, very rare) => maybe explained with bandwidth bug discovered with transport test
5 2) 1 out of 3 bits of content fails to migrate (destination peer never sees it);
6 suspicion: core packs two migration messages into one, and someone throws away the 2nd half!
7 => likely reproduced with new core api reliability test (which still fails)
8 3) client fails to connect to FS service for download (requests never make it to FS)
9 FS was running initially, but is shut down around the time the source peer (!)
10 is supposed to die; the OTHER FS service (the one that was supposed to die) is still up!
11 - TTL/priority calculations
12 - hot-path routing, load considerations
14 - active reply route caching design & implementation of service; gap extension!
18 - write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
19 - implement DV service
20 - implement DV library (looks done)
21 - implement DV transport plugin
23 - implement performance tests (needs tbench)
25 - needs more testing (especially F2F topology) & transport blacklisting
27 - only connect() sockets that are ready (select()) [Nils]
28 [On W32, we need to select after calling socket before doing connect etc.]
29 - add support for UNIX domain sockets [CG]
32 + use g_main_context_set_poll_func to integrate GTK with GNUnet Scheduler!? (YUCK!)
33 + OR: add scheduler API to enable integration with GTK main loop instead of doing our own select
34 + use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
35 and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
36 to integrate this with "gtk_main"? Docu says:
37 "It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
38 slightly more typing. See GMainLoop in the GLib documentation."
39 => so maybe it "just works"?
40 - implement glade loader
41 - implement main quit handler (file-quit and main window close)
42 - implement about menu handler
43 - add license to about dialog
44 - add authors to about dialog
45 - add translators to about dialog
46 - add documenters to about dialog
47 - add artists to about dialog
48 - test logo in about dialog
49 - test logo in main dialog (window icon)
50 - implement search dialog opening and actual search
51 - NS list in search dialog should use colors to offset our own namespaces from the others
52 - double-clicking on NS list in search dialog should move 'root' to keyword line
53 - double-clicking on search result in master list should open save-as dialog for CHK/LOC URIs
54 - right-clicking on search result should open menu that allows:
55 + viewing full meta data
57 + starting recursive download
58 + aborting active download
59 - right-clicking on NS list in search dialog should open menu that allows
60 + viewing full meta data
61 + deletion of namespace info
62 - master should add tab to main notebook with label with 'new' icon that allows starting of a search (same as via menu)
63 - tabs in notebook should contain:
64 + "X" to allow closing of tabs
65 + "play" to allow resuming of search OR "pause" to allow pausing of search
66 - implement open directory dialog
67 - implement new-pseudonym dialog
68 - implement publish dialog
70 + edit (meta data add, meta data del, meta data type population, keyword add (button, activate entry line),
71 keyword remove, anonymity level, priority, index/insert, normalize keywords,
72 previews, preview widget for file chooser!?)
73 + mark 'insert file' button inconsistent for directories
79 + open (import directory structure)
82 - pick appropriate sort-by columns for various tree view columns
83 - anonymity spin buttons should turn red on zero:
90 - transport-level disconnect (i.e. TCP) does not cause core-level
91 disconnect in a timely fashion (waits for connection timeout);
92 need to figure a way to make it near-instant in those cases
93 (i.e. rapid reduction in timeout on transport-level disconnect)
95 - good to have for transport/DV evaluation!
97 - implement DHT service
99 - implement performance tests
101 - better crash management (attach debugging support, capture and analyze
102 debug output, detect random vs. deterministic crashes)
103 - discover dependencies between services
104 => need UNIX domain sockets first!
105 - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
107 - datastore reservation (publishing)
108 - location URIs (publish, search, download)
109 - unindex on index failure
110 - utilize in-line files in meta data always (including in search results or
111 when download is triggered manually and for probes); currently the data is
112 only used when users do a general 'recursive' download
113 - non-anonymous FS service (needs DHT)
114 + DHT integration for search
115 + CS-DHT-functions (DHT-put of LOC)
116 + P2P-functions (DHT-get)
117 - collection API & tests
118 + gnunet-pseudonym (collection support)
119 - implement FS performance tests
125 - handle view-metadata toggle
126 - handle view-preview toggle
127 - implement API to get notifications about bandwidth assignments to individual peers
128 - implement API to get notifications about updates to liveness of individual peers (before disconnect)
129 - handle view-neighbours toggle
130 - extend peer dialog with green-yellow-red connectivity status lights
131 - implement statistics tabs
132 - handle view-statistics toggle
133 - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
134 - implement unindex operation (use dialog with all indexed files for selection)
135 - implement download by URI dialog; figure out where to display those downloads!
136 - figure out where in the GUI we should show active uploads/unindex operations and allow aborts
138 - design & implement new setup tool
142 - good to have for DV/DHT evaluation!
143 * Determine RC bugs and fix those!
145 - GNUNET_DATASTORE_cancel method not tested
147 - modify configuration to allow controlling connections for non-local starts
148 - testbed creation with topology (needs working F2F topology)
150 - implement testcases for distributed testing
151 - test basic peer re-configure
152 - test topology creation
153 - test churn generation
154 - consider changing API for peer-group termination to
155 call continuation when done
157 - finalize API design
160 - integration with transport service
161 * MYSQL database backends: [CG]
165 - reconstruct IBLOCKS from DBLOCKS if possible (during download; see FIXME in fs_download)
166 - add support for pushing "already seen" search results to FS service for bloomfilter (can wait)
167 - use different 'priority' for probe downloads vs. normal downloads
169 - better tracking of which config changes actually need to cause process restarts by ARM.
173 - expand bibliography
174 - convert documentation pages to books
175 - update books (especially for developers)
176 - create good Drupal theme for GNUnet
177 - make a NICE download page and figure out how to enable developers to publish TGZs nicely
178 - port "contact" page
179 - add content type for "todo" items?
180 * POSTGRES database backends: [CG]
183 * Determine RC bugs and fix those!
187 - SMTP transport backend
188 - HTTPS transport backend
189 + improved HTTPS support in MHD
191 - Implement method of learning our external addresses from
192 other peers; need some kind of threshold-based
193 scheme, limiting both the total number of addresses that we accept
194 this way as well as requiring multiple confirmations; also, we
195 should possibly try to confirm that the given address works for
196 us ourselves (loopback-style) before adding it to the list
197 + we may be able to simplify WELCOME messages (no need to add
198 addresses there anymore, but may help to learn them there anyway...).
199 + we probably want some kind of voting/counting for learning IP addresses
200 (maybe including IP addresses in ads proportional to how often others
201 report them? we at least need some protection against >64k HELLOs!),
202 + provide a way to give the user a list of "learned" IP addresses and
203 a way to easily "veto" addresses off the list!
204 => If MiM attacker uses vetoed address, blacklist the specific IP for
205 the presumed neighbour!
206 - implement gnunet-transport (transport configurator / tester)
207 - UPnP-based IP detection
208 (Note: build library always, build service when libxml2/etc. are available)
210 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
212 - expire 'ancient' HELLOs (those without valid addresses AND that
213 we have not 'used' (for their public keys) in a while; need a way
214 to track actual 'use')
215 - make sue we also trigger notifications whenever HELLOs expire
222 - should use hash map to look up sessions
224 - should use BIO instead of mmap
226 - need to periodically probe latency/transport cost changes & possibly switch transport
227 - should use hash map to look up Neighbours (service AND plugins!)
229 - check for duplicates on insertion (currently, same content is frequently
230 stored again [seen with KBLOCKS and SBLOCKS]!)
232 - merge multiple HELLOs of the same peer in the transmission queue
233 (theoretically reduces overhead; bounds message queue size)
234 - merge multiple iteration requests over "all" peers in the queue
235 (theoretically reduces overhead; bounds messgae queue size)
237 - use different queue prioritization for probe-downloads vs. normal downloads (!?)
241 - repeatedly resolve hostname and look up interfaces to determine our own IP
242 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
244 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
246 - testcase would be nice...