Skip to content

Changing Infohash from Unsupported Info-Fields #261

@da2ce7

Description

@da2ce7

Parent: #275

Hi @da2ce7, I've been thinking about changing the infohash again, and I do not like the side effect. It has a similar effect to the "source" file. As we change the infohash:

  • All the trackers listed on the torrent file are not going to work because the infohash has changed.
  • Peer can only download the torrent from other peers using the same tracker.

What we are doing is kind of creating a new "normalized" torrent but somehow splitting the swarm.

In a public index/tracker, I think we should generate the same torrent, only adding the linked/associated tracker in the announce list.

Originally posted by @josecelano in #260 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions