10
3
Fork
You've already forked sciop-cli
4

sciop-cli sync: Auto-replace repacked torrents #26

Open
opened 2025年06月26日 09:28:55 +02:00 by sneakers-the-rat · 0 comments

Depends on: Safeguarding/sciop#347
Depends on: Safeguarding/sciop#448

Now that we have qbittorrent adapter merged, once the server is capable of telling us about repacked torrents, we should add a command

sciop-cli sync repacks should be a command that

  • checks our configured clients for a list of infohashes of current torrents
  • sends those to /api/v1/uploads/repacks ( Safeguarding/sciop#448 )
  • gets a list of updated torrents
  • removes the torrent item in the client but not the files of the torrent from the disk
  • adds the updated torrent with the same path on disk as the torrent being updated.

The command should by default replace any torrents that have been marked as repacked by the uploader of the original torrents (see Safeguarding/sciop#448 ). however it should also display the presence of repacks by other accounts, and offer an option to apply a specific repack from a different account, e.g. by short hash. Bonus points would be to display these "extra" repacks along with the "description" field of the upload, which may contain information about the repack.

Depends on: https://codeberg.org/Safeguarding/sciop/issues/347 Depends on: https://codeberg.org/Safeguarding/sciop/issues/448 Now that we have qbittorrent adapter merged, once the server is capable of telling us about repacked torrents, we should add a command `sciop-cli sync repacks` should be a command that - checks our configured clients for a list of infohashes of current torrents - sends those to `/api/v1/uploads/repacks` ( https://codeberg.org/Safeguarding/sciop/issues/448 ) - gets a list of updated torrents - removes the *torrent item in the client* but not the *files of the torrent from the disk* - adds the updated torrent with the same path on disk as the torrent being updated. The command should by default replace any torrents that have been marked as repacked *by the uploader of the original torrents* (see https://codeberg.org/Safeguarding/sciop/issues/448 ). however it should also *display* the presence of repacks by other accounts, and offer an option to apply a specific repack from a different account, e.g. by short hash. Bonus points would be to display these "extra" repacks along with the "description" field of the upload, which may contain information about the repack.
Sign in to join this conversation.
No Branch/Tag specified
main
human-size
api-call
autopiecesize
v2-only
default-trackers
create-torrent
ci-init
v0.3.0
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
Labels
Clear labels
api
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Tech Debt
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Safeguarding/sciop-cli#26
Reference in a new issue
Safeguarding/sciop-cli
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?