Closed d47081 closed 1 year ago
In other point of view, by changing current implementation, we can lost possibility to add info hash versions for existing magnets with time.
Anyway, I don't know how to identify magnet else, but it info hash + owner IP
:/
As the solution, magnet could be identified by condition:
USER_IP + MAGNET_TIMESTAMP_ADDED
Closed so.
Fields used for distributed content identification so to prevent initiation new magnet on API sync, user can't change these fields after publication, just change other info, like description or trackers.
At this moment, user able to provide info hash v1 or v2 once, when it's was empty on magnet link sending.