Overwrite created by field in the torrent file

[josecelano]

Relates to: #284

We could overwrite the created by field in the torrent file with the value: Torrust Index/v3.0.0

Example torrent file in JSON:

{
   "created by": "imdl/0.1.13",
   "creation date": 1694545594,
   "encoding": "UTF-8",
   "info": {
      "length": 30,
      "name": "torrent-without-private-field.txt",
      "piece length": 16384,
      "pieces": "<hex>87 F9 9A 42 68 8D AE 18 E5 72 1D 7C 37 7B 88 91 E0 2D 08 9E</hex>"
   }
}

[cgbosse]

What benefit is there in this ?
Is it appropriate?
Should there be some form of traceability the creator?

@josecelano

[josecelano]

What benefit is there in this ? Is it appropriate? Should there be some form of traceability the creator?

@josecelano

It's a matter of consistency. We can consider the Index as:

• A simple storage for torrents without altering them. We keep the same infohash and we serve the same torrent that was uploaded.
• An application that handles a collection of torrents. It normalizes them, so they all have similar properties and attributes.

We are doing the second because we do not store the original torrent. We only keep the standards attributes and sometimes the original infohash can change. That final one is what we call the canonical infohash. Estricitkly speaking we have created a new torrent, so the Index is the creator. It creates a new torrent by using information from a previous one.

On the other hand, just overwriting the creator could give visibility to the project. That's a "marketing" reason to do it. I would do it due to the first reason :-)