diff options
author | Christian Grothoff <christian@grothoff.org> | 2011-06-10 11:07:37 +0000 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2011-06-10 11:07:37 +0000 |
commit | 4c141ec5e9ba1a0e8fd4bc266c0a2979a6ec1dd9 (patch) | |
tree | a3424143412d37e1141834e654699521e429061d | |
parent | 3d56d2b36ab23858e0d6a21271e96ea41538ec2f (diff) | |
download | gnunet-4c141ec5e9ba1a0e8fd4bc266c0a2979a6ec1dd9.tar.gz gnunet-4c141ec5e9ba1a0e8fd4bc266c0a2979a6ec1dd9.zip |
update
-rw-r--r-- | RATIONALE | 36 | ||||
-rw-r--r-- | README | 43 |
2 files changed, 39 insertions, 40 deletions
@@ -241,6 +241,8 @@ PROBLEM GROUP 6 (FS-APIs): | |||
241 | saves to disk on shutdown) | 241 | saves to disk on shutdown) |
242 | * FILENAME metadata is killed by ECRS/FSUI to avoid | 242 | * FILENAME metadata is killed by ECRS/FSUI to avoid |
243 | exposing HOME, but what if the user set it manually? | 243 | exposing HOME, but what if the user set it manually? |
244 | * The DHT was a generic data structure with no | ||
245 | support for ECRS-style block validation | ||
244 | 246 | ||
245 | SOLUTION: | 247 | SOLUTION: |
246 | * Eliminate threads from FS-APIs | 248 | * Eliminate threads from FS-APIs |
@@ -249,6 +251,10 @@ SOLUTION: | |||
249 | * Have API to manipulate sharing tree before | 251 | * Have API to manipulate sharing tree before |
250 | upload; have auto-construction modify FILENAME | 252 | upload; have auto-construction modify FILENAME |
251 | but allow user-modifications afterwards | 253 | but allow user-modifications afterwards |
254 | * DHT API was extended with a BLOCK API for content | ||
255 | validation by block type; validators for FS and | ||
256 | DHT block types were written; BLOCK API is also | ||
257 | used by gap routing code. | ||
252 | 258 | ||
253 | 259 | ||
254 | PROBLEM GROUP 7 (User experience): | 260 | PROBLEM GROUP 7 (User experience): |
@@ -258,20 +264,34 @@ PROBLEM GROUP 7 (User experience): | |||
258 | creates thousands of search results for the mime-type keyword | 264 | creates thousands of search results for the mime-type keyword |
259 | (problem with DB performance, network transmission, caching, | 265 | (problem with DB performance, network transmission, caching, |
260 | end-user display, etc.) | 266 | end-user display, etc.) |
267 | * Users that wanted to share important content had no way to | ||
268 | tell the system to replicate it more; replication was also | ||
269 | inefficient (this desired feature was sometimes called | ||
270 | "power" publishing or content pushing) | ||
261 | 271 | ||
262 | SOLUTION (draft, not done yet, details missing...): | 272 | SOLUTION: |
263 | * Canonicalize keywords (see suggestion on mailinglist end of | 273 | * Have option to canonicalize keywords (see suggestion on mailinglist end of |
264 | June 2009: keep consonants and sort those alphabetically); | 274 | June 2009: keep consonants and sort those alphabetically); not |
265 | while I think we must have an option to disable this feature | 275 | fully implemented yet |
266 | (for more private sharing), I do think it would make a reasonable | ||
267 | default | ||
268 | * When sharing directories, extract keywords first and then | 276 | * When sharing directories, extract keywords first and then |
269 | push keywords that are common in all files up to the | 277 | push keywords that are common in all files up to the |
270 | directory level; when processing an AND-ed query and a directory | 278 | directory level; when processing an AND-ed query and a directory |
271 | is found to match the result, do an inspection on the metadata | 279 | is found to match the result, do an inspection on the metadata |
272 | of the files in the directory to possibly produce further results | 280 | of the files in the directory to possibly produce further results |
273 | (requires downloading of the directory in the background) | 281 | (requires downloading of the directory in the background); |
274 | 282 | needs more testing | |
283 | * A desired replication level can now be specified and is tracked | ||
284 | in the datastore; migration prefers content with a high | ||
285 | replication level (which decreases as replicase are created) | ||
286 | => datastore format changed; we also took out a size field | ||
287 | that was redundant, so the overall overhead remains the same | ||
288 | * Peers with a full disk (or disabled migration) can now notify | ||
289 | other peers that they are not interested in migration right | ||
290 | now; as a result, less bandwidth is wasted pushing content | ||
291 | to these peers (and replication counters are not generally | ||
292 | decreased based on copies that are just discarded; naturally, | ||
293 | there is still no guarantee that the replicas will stay | ||
294 | available) | ||
275 | 295 | ||
276 | 296 | ||
277 | 297 | ||
@@ -21,7 +21,7 @@ Dependencies: | |||
21 | 21 | ||
22 | Please note that for many of its dependencies GNUnet requires very | 22 | Please note that for many of its dependencies GNUnet requires very |
23 | recent versions of the libraries which are often NOT to be found in | 23 | recent versions of the libraries which are often NOT to be found in |
24 | stable distributions in 2010. While using older packages may in some | 24 | stable distributions in 2011. While using older packages may in some |
25 | cases on some operating systems may seem to work in some limited | 25 | cases on some operating systems may seem to work in some limited |
26 | fashion, we are in many cases aware of serious problems with older | 26 | fashion, we are in many cases aware of serious problems with older |
27 | packages. Hence please make sure to use the versions listed below. | 27 | packages. Hence please make sure to use the versions listed below. |
@@ -87,9 +87,10 @@ location of the configuration file in this case. | |||
87 | Note that additional, per-user configuration files | 87 | Note that additional, per-user configuration files |
88 | (~/.gnunet/gnunet.conf) need to be created by each user (for example, | 88 | (~/.gnunet/gnunet.conf) need to be created by each user (for example, |
89 | by running gnunet-setup). Note that gnunet-setup is a separate | 89 | by running gnunet-setup). Note that gnunet-setup is a separate |
90 | download and requires GTK+; you can also edit the configuration file | 90 | download and requires recent versions of GTK+ and Glade; you can also |
91 | by hand, but this is not recommended. For more general information | 91 | edit the configuration file by hand, but this is not recommended. For |
92 | about the GNU build process read the INSTALL file. | 92 | more general information about the GNU build process read the INSTALL |
93 | file. | ||
93 | 94 | ||
94 | If you are compiling the code from subversion, you have to run | 95 | If you are compiling the code from subversion, you have to run |
95 | ". bootstrap" before ./configure. If you receive an error during the | 96 | ". bootstrap" before ./configure. If you receive an error during the |
@@ -143,20 +144,9 @@ to "$SERVICEHOME/data/hosts/" (where $SERVICEHOME is the directory | |||
143 | specified in the gnunet.conf configuration file). | 144 | specified in the gnunet.conf configuration file). |
144 | 145 | ||
145 | Now start the local node using "gnunet-arm -s". GNUnet should run 24/7 if | 146 | Now start the local node using "gnunet-arm -s". GNUnet should run 24/7 if |
146 | you want to maximize your anonymity. | 147 | you want to maximize your anonymity. |
147 | |||
148 | The GTK user interface is shipped separately. After downloading and | ||
149 | installing gnunet-gtk, you can invoke the GUI with: | ||
150 | |||
151 | $ gnunet-gtk | ||
152 | |||
153 | // FIXME: gnunet-qt is not yet supported in 0.9.x | ||
154 | For Qt/KDE users, there is also a QT user interface (also shipped | ||
155 | separately). If you install gnunet-qt, you can invoke the GUI with: | ||
156 | |||
157 | $ gnunet-qt | ||
158 | 148 | ||
159 | If you want to use the shell (part of this distribution), use | 149 | You should then be able to access GNUnet using the shell: |
160 | 150 | ||
161 | $ gnunet-search KEYWORD | 151 | $ gnunet-search KEYWORD |
162 | 152 | ||
@@ -168,11 +158,11 @@ to retrieve a file. The GNUNET_URI is printed by gnunet-search | |||
168 | together with a description. To publish files on GNUnet, use the | 158 | together with a description. To publish files on GNUnet, use the |
169 | "gnunet-publish" command. | 159 | "gnunet-publish" command. |
170 | 160 | ||
171 | // FIXME: auto-share is not yet supported in 0.9.x | ||
172 | In order to share files, the easiest way is to create a directory | ||
173 | with the files (and directories) that you want to share and run | ||
174 | 161 | ||
175 | $ nohup gnunet-auto-share NAME-OF-THE-DIRECTORY & | 162 | The GTK user interface is shipped separately. After downloading and |
163 | installing gnunet-gtk, you can invoke the GUI with: | ||
164 | |||
165 | $ gnunet-gtk | ||
176 | 166 | ||
177 | For further documentation, see our webpage. | 167 | For further documentation, see our webpage. |
178 | 168 | ||
@@ -231,17 +221,6 @@ network). However, we are not aware of this providing any advantages | |||
231 | at this point. | 221 | at this point. |
232 | 222 | ||
233 | 223 | ||
234 | |||
235 | Running the SMTP transport | ||
236 | ========================== | ||
237 | |||
238 | // NOTE: SMTP is not currently available in this version of GNUnet | ||
239 | Running GNUnet over SMTP (e-mail) is a bit more involved. Note that | ||
240 | you do not need to run all transports (only running the NAT transport | ||
241 | is the only thing that will not work). If you really want to do | ||
242 | P2P over SMTP, read the instructions at http://gnunet.org/smtp | ||
243 | |||
244 | |||
245 | Stay tuned | 224 | Stay tuned |
246 | ========== | 225 | ========== |
247 | 226 | ||