That's a very good start! I want to expand and elaborate why there is still room for improvements.
1. Many downloads are multi-part. Each part has its own link. Sometimes users want to replace 10 links by more or less links. As far as I understand this is now only possible through the text replacement, just like this:
Code:
http://lamelink1.local
http://lamelink2.local
http://lamelink3.local
can be matched and replaced by TM (text replacement!) in all posts by
Code:
http://leetlink1.local
http://leetlink2.local
http://leetlink3.local
OR even
Code:
http://leetlink1.local
http://leetlink2.local
This would be necessary for all bigger downloads since editing the single links manually is very much work. Did I get it right?
2. The text import for links replacements demands me delivering
Code:
http://lamelink1.local | http://leetlink1.local
What if the file counts don't match in cases where the packaging was altered? Also, this format is not very user friendly as most upload software and the hosting sites provide the links top down, as a list separated with a line break, just like:
Code:
http://leetlink1.local
http://leetlink2.local
http://leetlink3.local
3. What I really miss is a solution for feeding backup links that are replaced automatically by TM. That means I need a way for TM to look if I provided any backup links that are the replacement for the dead links and fill them in if it finds the links dead.
4. No complaining without providing a possible solution!
Heres what I would like to think you over:
For any group of links define a text file which contains the links on a specific hoster. Maybe this can already be done with "extract links".
Examples:
Code:
hotdownload-links-rapigator.txt
hotdownload-links-uploaded.to.txt
cooldownload-links-rapigator.txt
cooldownload-links-uploaded.to.txt
Format and procedure:
Just groups of links, each link in a group separated by a line break, each group separated by a configurable character. If link count does not match, reduce or raise the number of links according to what is found in the file.
Example:
Code:
http://lamelink1.specifichoster.local
http://lamelink2.specifichoster.local
http://lamelink3.specifichoster.local
#
http://leetlink1.specifichoster.local
http://leetlink2.specifichoster.local
http://leetlink3.specifichoster.local
#
http://leetlinknew1.specifichoster.local
http://leetlinknew2.specifichoster.local
http://leetlinknew3.specifichoster.local
#
http://lesslinkslink1.specifichoster.local
http://lesslinkslink2.specifichoster.local
When first group ist dead, it's replaced by the second, if second is dead by the third, then by the fourth. If there are no backup links left (or just one group, should be configurable), TM gives out a warning so that you can provide new backup links in time.
This file format has the big advantage that you can write to it with almost all tools and software every system has on board say hello to batch automation. You just append a line break and a char, then your backup links and all is done. It gives freedom for automation. Even with copy-paste it would be a snap to have backup links in place anytime as most people just can copy / paste their links into the text-file and are done.
I can be even more elaborate about this, but let's save that for a later point. That means, if you are interested in the idea.
Thanks for listening
Wurstmu