Questions about recent changes / new features

[Flinxxx]

What does the removal policy "Move to _old tag" mean/do?

What does the removal policy ordering options "Time added to vuze" and "Time added to tag" mean/do?
...Oh, maybe I get it: remove the oldest based on the selected 'time' option?

What about the update process is NOT anonymous? re: 5741.B22 Support for anonymous updating: Tools->Options->Interface->Start

Are the new variables "min_of_hour, hour_of_day," and "day_of_week" my computer's current time? Making the expression (isEQ(day_of_week, 2) && isGT(hour_of_day, 13) && isLT(hour_of_day, 23)) evaluate to true every Monday between 1pm and 11pm? But how would you use min_of_hour? the expression (isGT(hour_of_day, 13) && isGT(min_of_hour, 30)) is true from 13:31 to 13:59, then false from 14:00 to 14:30, then true again from 14:31 to 14:59 etc. It seemes to me that the "speed limits" > "schedule and settings" would be the best place to do whatever these are supposed to enable. Yes? No?

Is there any way to access the ‘added to tag’ time in tags? For example, send a "Restored" torrent back to the archive after 259,200 seconds. It would have to be via a function I suppose:
isGT( timeAdded("Restored"), 259200 ) or maybe isGT( sinceApplied("Restored"), 259200 )
That also assumes that it is actually seeded that entire time… oh well.

And an old feature, when does canArchive() evaluate true?

[parg]

Lot of questions!

Move to _old_tag means that for tag X, when a download is removed from it it is moved to a tag called X_Old. So, for example, you could use an 'execute-on-assign' action of 'stop' on X_Old.

Right

Core, SWT, plugin, version check should all be routed over Tor and downloaded via I2P when 'anonymous update' is selected

The new time variables are, as you say, based on your computer time. They allow somewhat similar things to the speed limit schedule thing as you say

I can add access to the added-to-tag time, I'll think about that

canArchive is true for completed and stopped downloads

[Flinxxx]

Thank you for all of the answers.

Move to _old_tag means that for tag X, when a download is removed from it it is moved to a tag called X_Old. So, for example, you could use an 'execute-on-assign' action of 'stop' on X_Old.
 

Would X_old make it into the archive? Currently any tags with tracker properties or constraints do not get archived with a torrent, would the X_old version of such a tag get archived?

[parg]

Should get archived - the ones that aren't archived are the one's that are automatically determined - the _Old tag itself doesn't have any such constraint.

[Mosko]

Has a new interface been introduced?

A few days ago the look of my search page changed dramatically with a grey box around the sources, and a lot more results on searches that look different and seem less relevent.

[parg]

The way results are shown has been switched from a web-browser to a native component. The results are exactly the same and not less relevant than before,

[deanomacbeano1971]

The way results are shown has been switched from a web-browser to a native component. The results are exactly the same and not less relevant than before,


 

Hi, im no expert when it comes to downloading and it could be because of something ive pressed (doubt it though) but wheni search for <...> how relevant is the skinny on smooching from nine years ago.
Ive searched for many of the same shows i was able to get with the last version of vuze and the results are similar ie totally nothing to do with what im searching for, if you can tell me where im going wrog id be very grateful, thanks

[rexieb]

seems like the pirate bay has been blocked in Australia, now the response to any search is very limited..I am not real savvy on how to create new templates..Can anyone advise if there are new templates available..Thanks