View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002521 | GNUnet | file-sharing service | public | 2012-08-25 19:15 | 2012-08-26 23:57 |
| Reporter | dad | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Platform | linux | OS | Debian | OS Version | sid |
| Product Version | 0.9.3 | ||||
| Summary | 0002521: gnunet-publish: Permit to automatically re-add metadata when adding new keyword with -u option | ||||
| Description | Hello, In “gnunet-publish” manpage I saw that the “--uri” permit to add new keywords/metadata and/or publish under a new namespace. Specifying the old metadata is cumbersome, the cut&past does not work as expected since the space between “:” and the value is significant "mimetype: text/plain" != "mimetype:text/plain" I find useful to add an option to automatically use the existent metadata, something like “--keep-metadata”. It may be only useful with the “--uri” option. This option should have a lower priority than the “--meta” option, this will permit to use all the previous metadata except a few. Using an empty value could remove any existing metadata of that type, but is not appropriate if several occurrences of the same metadata are present and we want to remove only one. So another option may be useful, something like “--remove-metadata "TYPE:VALUE"”, and if value is null, remove all occurrences. Regards | ||||
| Tags | No tags attached. | ||||
|
|
I put this feature request in “file-sharing service” since I do not find a category for the clients. |
|
|
While this is a fine suggestion, it is simply not possible: we don't have the meta data anymore, and we deliberately do not keep it around (as for inserted files, this would give information to an adversary compromising your system as to you being the origin of the file). Not to mention that you can use the --uri option to share URIs for which you never had the meta data or the file (not that it makes too much sense in most cases). So I don't really see a good way to implement this without (a) keeping more information around, which is risky; (b) doing significant additional implementation work; neither sounds like a good choice, especially as I don't see this as a commonly used feature. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-08-25 19:15 | dad | New Issue | |
| 2012-08-25 19:16 | dad | Note Added: 0006289 | |
| 2012-08-26 23:57 | Christian Grothoff | Note Added: 0006290 | |
| 2012-08-26 23:57 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2012-08-26 23:57 | Christian Grothoff | Status | new => closed |
| 2012-08-26 23:57 | Christian Grothoff | Resolution | open => won't fix |
