werwolfby/monitorrent

Fork 0

mirror of https://github.com/werwolfby/monitorrent.git synced 2026-10-15 05:52:15 +00:00

[GH-ISSUE #113] One-time download without tracking changes #76

New issue

Open

opened 2026-10-13 19:47:05 +00:00 by bsakaguchi · 9 comments

bsakaguchi commented

2026-10-13 19:47:05 +00:00

Owner

Originally created by @werwolfby on GitHub (Jul 14, 2016).
Original GitHub issue: https://github.com/werwolfby/monitorrent/issues/113

Originally assigned to: @werwolfby on GitHub.

Add topic for one time download for support trackers, and ignore topic for updates.
Support for magnet-links and file upload:

When file is chosen display URL instead of BROWSE on the button.

Originally created by @werwolfby on GitHub (Jul 14, 2016). Original GitHub issue: https://github.com/werwolfby/monitorrent/issues/113 Originally assigned to: @werwolfby on GitHub. Add topic for one time download for support trackers, and ignore topic for updates. Support for magnet-links and file upload: ![Mockup](https://cloud.githubusercontent.com/assets/705754/16848510/c809eb58-49fe-11e6-81eb-951bc4059498.png) When file is chosen display URL instead of BROWSE on the button.

bsakaguchi added the

feature

label

2026-10-13 19:47:05 +00:00

bsakaguchi commented

2026-10-13 19:47:08 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 14, 2016):

And where is one-time download button? :)

@werwolfby commented on GitHub (Jul 14, 2016): And where is one-time download button? :)

bsakaguchi commented

2026-10-13 19:47:09 +00:00

Author

Owner

@DSilence commented on GitHub (Jul 14, 2016):

Fixed it for ya

@DSilence commented on GitHub (Jul 14, 2016): Fixed it for ya ![c809eb58-49fe-11e6-81eb-951bc4059498](https://cloud.githubusercontent.com/assets/3896043/16850573/77dcf1de-4a08-11e6-9a45-bbe99c19a51a.png)

bsakaguchi commented

2026-10-13 19:47:09 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 14, 2016):

Should we support convert one-time topics to "monitorable" topics and vise versa?
It can be useful if you made mistake and clicked wrong button?

@werwolfby commented on GitHub (Jul 14, 2016): Should we support convert one-time topics to "monitorable" topics and vise versa? It can be useful if you made mistake and clicked wrong button?

bsakaguchi commented

2026-10-13 19:47:10 +00:00

Author

Owner

@DSilence commented on GitHub (Jul 14, 2016):

I think it makes a good gombination with "pause" feature. A one-time download is topic which is initially paused (after first download). Later, you can unpause it any time.

@DSilence commented on GitHub (Jul 14, 2016): I think it makes a good gombination with "pause" feature. A one-time download is topic which is initially paused (after first download). Later, you can unpause it any time.

bsakaguchi commented

2026-10-13 19:47:10 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 14, 2016):

Good idea, I tried to combine the two features, but without success.
I like the idea.
@kijojo what do you think?

@werwolfby commented on GitHub (Jul 14, 2016): Good idea, I tried to combine the two features, but without success. I like the idea. @kijojo what do you think?

bsakaguchi commented

2026-10-13 19:47:11 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 14, 2016):

Replace buttons: "Add" to "Monitor" and onetime to "Download"?

Add by default don't execute topic right after add, should it?
While Download have to do it and pause topic after success execute only.

@werwolfby commented on GitHub (Jul 14, 2016): Replace buttons: **"Add"** to **"Monitor"** and onetime to **"Download"**? **Add** by default don't execute topic right after add, should it? While **Download** have to do it and pause topic after success execute only.

bsakaguchi commented

2026-10-13 19:47:11 +00:00

Author

Owner

@kijojo commented on GitHub (Jul 14, 2016):

Pause feature is more about whether download files or not and not about checking topic for updates

@kijojo commented on GitHub (Jul 14, 2016): Pause feature is more about whether download files or not and not about checking topic for updates

bsakaguchi commented

2026-10-13 19:47:12 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 25, 2016):

@werwolfby commented on GitHub (Jul 25, 2016): ![new design](https://cloud.githubusercontent.com/assets/705754/17119326/d0352b9e-52cd-11e6-9cf0-0805cc691a2e.png)

bsakaguchi commented

2026-10-13 19:47:12 +00:00

Author

Owner

@werwolfby commented on GitHub (Jul 25, 2016):

magnet-link disable add button and allow only one-time dowload.
Should parse magnet link in someway to extract display_name and display it in topics list.
browse allow to select torrent file, replace URL or magnet link to File name, disable add button and allow only one-time dowload
add add new topic for monitoring
In case when someone press one-time by mistake instead of add, there should be someway to convert one-time download topic into monitoring topic, and vice-versa. Still think that this behavior should be combined with pause feature (#30).
magnet-link and browse-based files can't be converted to monitorrent topics. After one-time success download it have to be converter to stopped without ability to convert it into monitoring topic, because we don't know how to track changes.
We should process magnet link inside Monitorrent, for example downloader (#102) can't work with magnet-link, instead it have to be converter to torrent file and downloaded,
If torrent client will be unavailable for some reason, add one-time download file will be postponed to the next execute phase.
add by default don't execute topic right after add, should it?
one-time have to do it and pause topic after success execute only.
Because we can't get title for magnet-link we should not show any edit form for it. But it is required field: display_name, we should handle it somehow (let it be magnet link itselft for now).
Browse-based files doesn't have display_name as well, but we can use filename.

kijojo: Pause feature is more about whether download files or not and not about checking topic for updates

@kijojo: not sure that I understand you. According to #30, it is exactly about pause checking, not pause current downloads in torrent client. We have to think about action names intersection with #79.

@kijojo, @DSilence: we need to make final decision, and task is ready for implementation.

@werwolfby commented on GitHub (Jul 25, 2016): 1. **magnet-link** disable **add** button and allow only **one-time** dowload. Should parse magnet link in someway to extract display_name and display it in topics list. 2. **browse** allow to select torrent file, replace _**URL or magnet link**_ to _**File name**_, disable **add** button and allow only **one-time** dowload 3. **add** add new topic for **monitoring** 4. In case when someone press **one-time** by mistake instead of **add**, there should be someway to convert **one-time** download topic into **monitoring** topic, and vice-versa. Still think that this behavior should be combined with pause feature (#30). 5. **magnet-link** and **browse**-based files can't be converted to **monitorrent** topics. After one-time success download it have to be converter to stopped without ability to convert it into **monitoring** topic, because we don't know how to track changes. 6. We should process magnet link inside **Monitorrent**, for example **downloader** (#102) can't work with magnet-link, instead it have to be converter to torrent file and downloaded, 7. If torrent client will be unavailable for some reason, add one-time download file will be postponed to the next **execute** phase. 8. **add** by default don't execute topic right after add, should it? 9. **one-time** have to do it and pause topic after success execute only. 10. Because we can't get title for **magnet-link** we should not show any edit form for it. But it is required field: **display_name**, we should handle it somehow (let it be **magnet link** itselft for now). 11. **Browse**-based files doesn't have **display_name** as well, but we can use filename. > kijojo: Pause feature is more about whether download files or not and not about checking topic for updates @kijojo: not sure that I understand you. According to #30, it is exactly about pause checking, not pause current downloads in torrent client. We have to think about action names intersection with #79. @kijojo, @DSilence: we need to make final decision, and task is ready for implementation.