TODO 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551
  1. $Id$
  2. Legend:
  3. SPEC!! - Not specified
  4. SPEC - Spec not finalized
  5. N - nick claims
  6. R - arma claims
  7. P - phobos claims
  8. S - Steven claims
  9. M - Matt claims
  10. J - Jeff claims
  11. - Not done
  12. * Top priority
  13. . Partially done
  14. o Done
  15. d Deferrable
  16. D Deferred
  17. X Abandoned
  18. For Tor 0.2.0.x-rc:
  19. R - Figure out the autoconf problem with adding a fallback consensus.
  20. R - add a geoip file
  21. W - figure out license
  22. R - let bridges set relaybandwidthrate as low as 5kb
  23. o we need a config option to turn off proposal 109 behavior,
  24. RK- make it easier to set up a private tor network on your own computer
  25. is very hard.
  26. - FAQ entry which is wrong
  27. o Make BEGIN_DIR mandatory for asking questions of bridge authorities?
  28. (but only for bridge descriptors. not for ordinary cache stuff.)
  29. o Implement connection_dir_is_encrypted().
  30. o set up a filter to not answer any bridge descriptors on a
  31. non-encrypted request
  32. o write a tor-gencert man page
  33. . geoip caching and publishing for bridges
  34. d Track consecutive time up, not time since last-forgotten IP.
  35. - Mention in dir-spec.txt
  36. - Mention in control-spec.txt
  37. D have normal relays report geoip stats too.
  38. D different thresholds for bridges than for normal relays.
  39. o bridge relays round geoip stats *up*, not down.
  40. R - bridge communities
  41. . spec
  42. . deploy
  43. - man page entries for Alternate*Authority config options
  44. o there's a config option with a password and somehow use an
  45. http header and check it
  46. - clients who have a password configured decide to ask their bridge
  47. authority for a networkstatus
  48. - be able to have bridges that aren't in your torrc
  49. Things we'd like to do in 0.2.0.x:
  50. o if we notice a cached-status directory and we're not serving v2 dir
  51. info and it's old enough, delete it.
  52. o same with cached-routers*.
  53. N - document the "3/4 and 7/8" business in the clients fetching consensus
  54. documents timeline.
  55. R - then document the bridge user download timeline.
  56. N - Before the feature freeze:
  57. - 105+TLS, if possible.
  58. . TLS backend work
  59. - New list of ciphers for clients
  60. o Servers detect new ciphers, and only send ID cert when they
  61. get an older cipher list, and only request client cert when
  62. they get an older cipher list.
  63. - Clients only send certificates when asked for them.
  64. o Servers disable callback once negotiation is finished, so
  65. that renegotiation happens according to the old rules.
  66. o Clients initiate renegotiation immediately on completing
  67. a v2 connection.
  68. o Servers detect renegotiation, and if there is now a client
  69. cert, they adust the client ID.
  70. o Detect.
  71. o Adjust.
  72. - New revised handshake: post-TLS:
  73. - start by sending VERSIONS cells
  74. - once we have a version, send a netinfo and become open
  75. - Ban most cell types on a non-OPEN connection.
  76. - NETINFO fallout
  77. - Don't extend a circuit over a noncanonical connection with
  78. mismatched address.
  79. - Learn our outgoing IP address from netinfo cells?
  80. - Bugs.
  81. - Bug reports Roger has heard along the way that don't have enough
  82. details/attention to solve them yet.
  83. - arma noticed that when his network went away and he tried
  84. a new guard node and the connect() syscall failed to it,
  85. the guard wasn't being marked as down. 0.2.0.x.
  86. - after being without network for 12 hours, arma's tor decided
  87. it couldn't fetch any network statuses, and never tried again
  88. even when the network came back and arma clicked on things.
  89. also 0.2.0.
  90. R - for above two, roger should turn them into flyspray entry.
  91. o we should do another bandwidth test every 12 hours or something
  92. if we're showing less than 50KB and our bandwidthrate says we can
  93. do more than that. I think some servers are forgetting the results
  94. of their first test, and then never seeing use.
  95. - Proposals:
  96. o 101: Voting on the Tor Directory System (plus 103)
  97. N - Use if-modified-since on consensus download
  98. - Controller support
  99. D GETINFO to get consensus
  100. N - Event when new consensus arrives
  101. . 111: Prioritize local traffic over relayed.
  102. R - Merge into tor-spec.txt.
  103. - Refactoring:
  104. . Make cells get buffered on circuit, not on the or_conn.
  105. . Switch to pool-allocation for cells?
  106. N - Benchmark pool-allocation vs straightforward malloc.
  107. N - Adjust memory allocation logic in pools to favor a little less
  108. slack memory.
  109. . Remove socketpair-based bridges conns, and the word "bridge". (Use
  110. shared (or connected) buffers for communication, rather than sockets.)
  111. . Implement
  112. N - Handle rate-limiting on directory writes to linked directory
  113. connections in a more sensible manner.
  114. Nick thinks he did this already?
  115. N - Find more ways to test this.
  116. (moria doesn't rate limit, so testing on moria not so good.)
  117. - Documentation
  118. - HOWTO for DNSPort. See tup's wiki page.
  119. . Document transport and natdport in a good HOWTO.
  120. N - Quietly document NT Service options: revise (or create) FAQ entry
  121. R - make sure you solved bug 556
  122. P - Make documentation realize that location of system configuration file
  123. will depend on location of system defaults, and isn't always /etc/torrc.
  124. P - Figure out why dll's compiled in mingw don't work right in WinXP.
  125. P - create a "make win32-bundle" for vidalia-privoxy-tor-torbutton bundle
  126. Planned for 0.2.1.x:
  127. - anonymity concern: since our is-consensus-fresh-enough check is
  128. sloppy so clients will actually work when a consensus wasn't formed,
  129. does that mean that if users are idle for 5 hours and then click on
  130. something, we will immediately use the old descriptors we've got,
  131. while we try fetching the newer descriptors?
  132. related to bug 401.
  133. . Finish path-spec.txt
  134. - More prominently, we should have a recommended apps list.
  135. - recommend pidgin (gaim is renamed)
  136. - unrecommend IE because of ftp:// bug.
  137. - we should add a preamble to tor-design saying it's out of date.
  138. - Refactor networkstatus generation:
  139. - Include "v" line in getinfo values.
  140. - config option __ControllerLimit that hangs up if there are a limit
  141. of controller connections already.
  142. - Features (other than bridges):
  143. - Audit how much RAM we're using for buffers and cell pools; try to
  144. trim down a lot.
  145. - Base relative control socket paths on datadir.
  146. - Make TrackHostExits expire TrackHostExitsExpire seconds after their
  147. *last* use, not their *first* use.
  148. P - Plan a switch to polipo. Perhaps we'll offer two http proxies in
  149. the future.
  150. P - Consider creating special Tor-Polipo-Vidalia test packages,
  151. requested by Dmitri Vitalev
  152. - Create packages for Nokia 800, requested by Chris Soghoian
  153. - mirror tor downloads on (via) tor dir caches
  154. . spec
  155. - deploy
  156. - interface for letting soat modify flags that authorities assign
  157. . spec
  158. - proposal 118 if feasible and obvious
  159. - Maintain a skew estimate and use ftime consistently.
  160. - Tor logs the libevent version on startup, for debugging purposes.
  161. This is great. But it does this before configuring the logs, so
  162. it only goes to stdout and is then lost.
  163. - Deprecations:
  164. - can we deprecate 'getinfo network-status'?
  165. - can we deprecate the FastFirstHopPK config option?
  166. - Bridges:
  167. . Bridges users (rudimentary version)
  168. . Ask all directory questions to bridge via BEGIN_DIR.
  169. - use the bridges for dir fetches even when our dirport is open.
  170. - drop 'authority' queries if they're to our own identity key; accept
  171. them otherwise.
  172. - give extend_info_t a router_purpose again
  173. d Limit to 2 dir, 2 OR, N SOCKS connections per IP.
  174. - Or maybe close connections from same IP when we get a lot from one.
  175. - Or maybe block IPs that connect too many times at once.
  176. - Do TLS connection rotation more often than "once a week" in the
  177. extra-stable case.
  178. - Streamline how we pick entry nodes: Make choose_random_entry() have
  179. less magic and less control logic.
  180. - when somebody uses the controlport as an http proxy, give them
  181. a "tor isn't an http proxy" error too like we do for the socks port.
  182. - we try to build 4 test circuits to break them over different
  183. servers. but sometimes our entry node is the same for multiple
  184. test circuits. this defeats the point.
  185. - enforce a lower limit on MaxCircuitDirtiness and CircuitBuildTimeout.
  186. - configurable timestamp granularity. defaults to 'seconds'.
  187. - consider making 'safelogging' extend to info-level logs too.
  188. - we should consider a single config option TorPrivateNetwork that
  189. turns on all the config options for running a private test tor
  190. network. having to keep updating all the tools, and the docs,
  191. just isn't working.
  192. - consider whether a single Guard flag lets us distinguish between
  193. "was good enough to be a guard when we picked it" and "is still
  194. adequate to be used as a guard even after we've picked it". We should
  195. write a real proposal for this.
  196. - switch out privoxy in the bundles and replace it with polipo.
  197. - make the new tls handshake blocking-resistant.
  198. - figure out some way to collect feedback about what countries are using
  199. bridges, in a way that doesn't screw anonymity too much.
  200. - let tor dir mirrors proxy connections to the tor download site, so
  201. if you know a bridge you can fetch the tor software.
  202. - more strategies for distributing bridge addresses in a way that
  203. doesn't rely on knowing somebody who runs a bridge for you.
  204. - A way to adjust router status flags from the controller. (How do we
  205. prevent the authority from clobbering them soon afterward?)
  206. - Bridge authorities should do reachability testing but only on the
  207. purpose==bridge descriptors they have.
  208. - Clients should estimate their skew as median of skew from servers
  209. over last N seconds.
  210. - Investigate RAM use in Tor servers.
  211. - Start on the WSAENOBUFS solution.
  212. - Start on Windows auto-update for Tor
  213. Deferred from 0.2.0.x:
  214. - Proposals
  215. - 113: Simplifying directory authority administration
  216. - 110: prevent infinite-length circuits (phase one)
  217. - 118: Listen on and advertise multiple ports:
  218. - Tor should be able to have a pool of outgoing IP addresses that it is
  219. able to rotate through. (maybe. Possible overlap with proposal 118.)
  220. - config option to publish what ports you listen on, beyond
  221. ORPort/DirPort. It should support ranges and bit prefixes (?) too.
  222. (This is very similar to proposal 118.)
  223. - 117: IPv6 Exits
  224. - Internal code support for ipv6:
  225. o Clone ipv6 functions (inet_ntop, inet_pton) where they don't exist.
  226. - Most address variables need to become tor_addr_t
  227. - Teach resolving code how to handle ipv6.
  228. - Teach exit policies about ipv6 (consider ipv4/ipv6 interaction!)
  229. - Features
  230. - Let controller set router flags for authority to transmit, and for
  231. client to use.
  232. - add an 'exit-address' line in the descriptor for servers that exit
  233. from something that isn't their published address.
  234. - More work on AvoidDiskWrites?
  235. - Features
  236. - Make a TCP DNSPort
  237. - Protocol work
  238. - MAYBE kill stalled circuits rather than stalled connections. This is
  239. possible thanks to cell queues, but we need to consider the anonymity
  240. implications.
  241. - Implement TLS shutdown properly when possible.
  242. - Bugs
  243. - If the client's clock is too far in the past, it will drop (or just not
  244. try to get) descriptors, so it'll never build circuits.
  245. - Refactoring
  246. - Make resolves no longer use edge_connection_t unless they are actually
  247. _on_ a socks connection: have edge_connection_t and (say)
  248. dns_request_t both extend an edge_stream_t, and have p_streams and
  249. n_streams both be linked lists of edge_stream_t.
  250. - Generate torrc.{complete|sample}.in, tor.1.in, the HTML manual, and the
  251. online config documentation from a single source.
  252. - Move all status info out of routerinfo into local_routerstatus. Make
  253. "who can change what" in local_routerstatus explicit. Make
  254. local_routerstatus (or equivalent) subsume all places to go for "what
  255. router is this?"
  256. - Blocking/scanning-resistance
  257. - It would be potentially helpful to respond to https requests on
  258. the OR port by acting like an HTTPS server.
  259. - Do we want to maintain our own set of entryguards that we use as
  260. next hop after the bridge? Open research question; let's say no
  261. for 0.2.0 unless we learn otherwise.
  262. - Some mechanism for specifying that we want to stop using a cached
  263. bridge.
  264. - Build:
  265. - Detect correct version of libraries from autoconf script.
  266. Future versions:
  267. - deprecate router_digest_is_trusted_dir() in favor of
  268. router_get_trusteddirserver_by_digest()
  269. - See also Flyspray tasks.
  270. - See also all OPEN/ACCEPTED proposals.
  271. - See also all items marked XXXX and FFFF in the code.
  272. - Protocol:
  273. - Our current approach to block attempts to use Tor as a single-hop proxy
  274. is pretty lame; we should get a better one.
  275. - Allow small cells and large cells on the same network?
  276. - Cell buffering and resending. This will allow us to handle broken
  277. circuits as long as the endpoints don't break, plus will allow
  278. connection (tls session key) rotation.
  279. - Implement Morphmix, so we can compare its behavior, complexity,
  280. etc. But see paper breaking morphmix.
  281. - Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
  282. link crypto, unless we can bully DTLS into it.
  283. - Need a relay teardown cell, separate from one-way ends.
  284. (Pending a user who needs this)
  285. - Handle half-open connections: right now we don't support all TCP
  286. streams, at least according to the protocol. But we handle all that
  287. we've seen in the wild.
  288. (Pending a user who needs this)
  289. - Directory system
  290. - BEGIN_DIR items
  291. X turn the received socks addr:port into a digest for setting .exit
  292. - handle connect-dir streams that don't have a chosen_exit_name set.
  293. - Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
  294. - Add an option (related to AvoidDiskWrites) to disable directory
  295. caching. (Is this actually a good idea??)
  296. - Add d64 and fp64 along-side d and fp so people can paste status
  297. entries into a url. since + is a valid base64 char, only allow one
  298. at a time. Consider adding to controller as well.
  299. - Some back-out mechanism for auto-approval on authorities
  300. - a way of rolling back approvals to before a timestamp
  301. - Consider minion-like fingerprint file/log combination.
  302. - Have new people be in limbo and need to demonstrate usefulness
  303. before we approve them.
  304. - Hidden services:
  305. - Standby/hotswap/redundant hidden services.
  306. . Update the hidden service stuff for the new dir approach. (Much
  307. of this will be superseded by 114.)
  308. - switch to an ascii format, maybe sexpr?
  309. - authdirservers publish blobs of them.
  310. - other authdirservers fetch these blobs.
  311. - hidserv people have the option of not uploading their blobs.
  312. - you can insert a blob via the controller.
  313. - and there's some amount of backwards compatibility.
  314. - teach clients, intro points, and hidservs about auth mechanisms.
  315. - come up with a few more auth mechanisms.
  316. - auth mechanisms to let hidden service midpoint and responder filter
  317. connection requests.
  318. - Let each hidden service (or other thing) specify its own
  319. OutboundBindAddress?
  320. - Hidserv offerers shouldn't need to define a SocksPort
  321. - Server operation
  322. X When we notice a 'Rejected: There is already a named server with
  323. this nickname' message... or maybe instead when we see in the
  324. networkstatuses that somebody else is Named with the name we
  325. want: warn the user, send a STATUS_SERVER message, and fall back
  326. to unnamed.
  327. - If the server is spewing complaints about raising your ulimit -n,
  328. we should add a note about this to the server descriptor so other
  329. people can notice too.
  330. - When we hit a funny error from a dir request (eg 403 forbidden),
  331. but tor is working and happy otherwise, and we haven't seen many
  332. such errors recently, then don't warn about it.
  333. - Controller
  334. - Implement missing status events and accompanying getinfos
  335. - DIR_REACHABLE
  336. - BAD_DIR_RESPONSE (Unexpected directory response; maybe we're behind
  337. a firewall.)
  338. - BAD_PROXY (Bad http or https proxy)
  339. - UNRECOGNIZED_ROUTER (a nickname we asked for is unavailable)
  340. - Status events related to hibernation
  341. - something about failing to parse our address?
  342. from resolve_my_address() in config.c
  343. - sketchy OS, sketchy threading
  344. - too many onions queued: threading problems or slow CPU?
  345. - Implement missing status event fields:
  346. - TIMEOUT on CHECKING_REACHABILITY
  347. - GETINFO status/client, status/server, status/general: There should be
  348. some way to learn which status events are currently "in effect."
  349. We should specify which these are, what format they appear in, and so
  350. on.
  351. - More information in events:
  352. - Include bandwidth breakdown by conn->type in BW events.
  353. - Change circuit status events to give more details, like purpose,
  354. whether they're internal, when they become dirty, when they become
  355. too dirty for further circuits, etc.
  356. - Change stream status events analogously.
  357. - Expose more information via getinfo:
  358. - import and export rendezvous descriptors
  359. - Review all static fields for additional candidates
  360. - Allow EXTENDCIRCUIT to unknown server.
  361. - We need some way to adjust server status, and to tell tor not to
  362. download directories/network-status, and a way to force a download.
  363. - Make everything work with hidden services
  364. - Performance/resources
  365. - per-conn write buckets
  366. - separate config options for read vs write limiting
  367. (It's hard to support read > write, since we need better
  368. congestion control to avoid overfull buffers there. So,
  369. defer the whole thing.)
  370. - Look into pulling serverdescs off buffers as they arrive.
  371. - Rate limit exit connections to a given destination -- this helps
  372. us play nice with websites when Tor users want to crawl them; it
  373. also introduces DoS opportunities.
  374. - Consider truncating rather than destroying failed circuits,
  375. in order to save the effort of restarting. There are security
  376. issues here that need thinking, though.
  377. - Handle full buffers without totally borking
  378. - Rate-limit OR and directory connections overall and per-IP and
  379. maybe per subnet.
  380. - Misc
  381. - Hold-open-until-flushed now works by accident; it should work by
  382. design.
  383. - Display the reasons in 'destroy' and 'truncated' cells under
  384. some circumstances?
  385. - Make router_is_general_exit() a bit smarter once we're sure what
  386. it's for.
  387. - Automatically determine what ports are reachable and start using
  388. those, if circuits aren't working and it's a pattern we
  389. recognize ("port 443 worked once and port 9001 keeps not
  390. working").
  391. - Security
  392. - some better fix for bug #516?
  393. - don't do dns hijacking tests if we're reject *:* exit policy?
  394. (deferred until 0.1.1.x is less common)
  395. - Directory guards
  396. - Mini-SoaT:
  397. - Servers might check certs for known-good ssl websites, and if
  398. they come back self-signed, declare themselves to be
  399. non-exits. Similar to how we test for broken/evil dns now.
  400. - Authorities should try using exits for http to connect to some
  401. URLS (specified in a configuration file, so as not to make the
  402. List Of Things Not To Censor completely obvious) and ask them
  403. for results. Exits that don't give good answers should have
  404. the BadExit flag set.
  405. - Alternatively, authorities should be able to import opinions
  406. from Snakes on a Tor.
  407. - More consistent error checking in router_parse_entry_from_string().
  408. I can say "banana" as my bandwidthcapacity, and it won't even squeak.
  409. - Bind to random port when making outgoing connections to Tor servers,
  410. to reduce remote sniping attacks.
  411. - Audit everything to make sure rend and intro points are just as
  412. likely to be us as not.
  413. - Do something to prevent spurious EXTEND cells from making
  414. middleman nodes connect all over. Rate-limit failed
  415. connections, perhaps?
  416. - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
  417. - Needs thinking
  418. - Now that we're avoiding exits when picking non-exit positions,
  419. we need to consider how to pick nodes for internal circuits. If
  420. we avoid exits for all positions, we skew the load balancing. If
  421. we accept exits for all positions, we leak whether it's an
  422. internal circuit at every step. If we accept exits only at the
  423. last hop, we reintroduce Lasse's attacks from the Oakland paper.
  424. - Windows server usability
  425. - Solve the ENOBUFS problem.
  426. - make tor's use of openssl operate on buffers rather than sockets,
  427. so we can make use of libevent's buffer paradigm once it has one.
  428. - make tor's use of libevent tolerate either the socket or the
  429. buffer paradigm; includes unifying the functions in connect.c.
  430. - We need a getrlimit equivalent on Windows so we can reserve some
  431. file descriptors for saving files, etc. Otherwise we'll trigger
  432. asserts when we're out of file descriptors and crash.
  433. - Merge code from Urz into libevent
  434. - Make Tor use evbuffers.
  435. - Documentation
  436. - a way to generate the website diagrams from source, so we can
  437. translate them as utf-8 text rather than with gimp. (svg? or
  438. imagemagick?)
  439. . Flesh out options_description array in src/or/config.c
  440. . multiple sample torrc files
  441. . figure out how to make nt service stuff work?
  442. . Document it.
  443. - Refactor tor man page to divide generally useful options from
  444. less useful ones?
  445. - Add a doxygen style checker to make check-spaces so nick doesn't drift
  446. too far from arma's undocumented styleguide. Also, document that
  447. styleguide in HACKING. (See r9634 for example.)
  448. - exactly one space at beginning and at end of comments, except i
  449. guess when there's line-length pressure.
  450. - if we refer to a function name, put a () after it.
  451. - only write <b>foo</b> when foo is an argument to this function.
  452. - doxygen comments must always end in some form of punctuation.
  453. - capitalize the first sentence in the doxygen comment, except
  454. when you shouldn't.
  455. - avoid spelling errors and incorrect comments. ;)
  456. - Packaging
  457. - The Debian package now uses --verify-config when (re)starting,
  458. to distinguish configuration errors from other errors. Perhaps
  459. the RPM and other startup scripts should too?
  460. - add a "default.action" file to the tor/vidalia bundle so we can
  461. fix the https thing in the default configuration:
  462. http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort
  463. - Related tools
  464. - Patch privoxy and socks protocol to pass strings to the browser.
  465. Documentation, non-version-specific.
  466. - Specs
  467. - Mark up spec; note unclear points about servers
  468. NR - write a spec appendix for 'being nice with tor'
  469. - Specify the keys and key rotation schedules and stuff
  470. - Mention controller libs someplace.
  471. - Remove need for HACKING file.
  472. - document http://wiki.noreply.org/noreply/TheOnionRouter/TransparentProxy on freebsd and osx
  473. P - figure out why x86_64 won't build rpms from tor.spec
  474. P - figure out spec files for bundles of vidalia-tor-polipo
  475. P - figure out polipo install scripts for bundles of vidalia-tor-polipo on osx, win32
  476. - figure out selinux policy for tor
  477. P - change packaging system to more automated and specific for each
  478. platform, suggested by Paul Wouter
  479. P - Setup repos for redhat and suse rpms & start signing the rpms the
  480. way package management apps prefer
  481. Website:
  482. J - tor-in-the-media page
  483. P - Figure out licenses for website material.
  484. (Phobos reccomends the Open Publication License at
  485. http://opencontent.org/openpub/)
  486. P - put the logo on the website, in source form, so people can put it on
  487. stickers directly, etc.
  488. P - put the source image for the stickers on the website, so people can
  489. print their own
  490. P - figure out a license for the logos and docs we publish (trademark
  491. figures into this)
  492. (Phobos reccomends the Open Publication License at
  493. http://opencontent.org/openpub/)
  494. R - make a page with the hidden service diagrams.
  495. P - ask Jan/Jens to be the translation coordinator? add to volunteer page.
  496. - add a page for localizing all tor's components.
  497. - It would be neat if we had a single place that described _all_ the
  498. tor-related tools you can use, and what they give you, and how well they
  499. work. Right now, we don't give a lot of guidance wrt
  500. torbutton/foxproxy/privoxy/polipo in any consistent place.
  501. P - create a 'blog badge' for tor fans to link to and feature on their
  502. blogs. A sample can be found at http://interloper.org/tmp/tor/tor-button.png
  503. - Tor mirrors
  504. - make a mailing list with the mirror operators
  505. - make an automated tool to check /project/trace/ at mirrors to
  506. learn which ones are lagging behind.
  507. - auto (or manually) cull the mirrors that are broken; and
  508. contact their operator?
  509. - a set of instructions for mirror operators to make their apaches
  510. serve our charsets correctly, and bonus points for language
  511. negotiation.
  512. - figure out how to load-balance the downloads across mirrors?
  513. - ponder how to get users to learn that they should google for
  514. "tor mirrors" if the main site is blocked.
  515. - find a mirror volunteer to coordinate all of this
  516. Blog todo:
  517. - A "Tor calendar" so we can list upcoming talks, etc?
  518. - Link to the blog from the main Tor website