Brand new UI | Tons of new/optimized functionality | *Much* more Usenet content available ( deobfuscation support ) | FREE Download

NewsLeecher Version History

See what has changed so far, during the history of NewsLeecher.

+: Added a "Detailed Spam Logging" option to the setup dialog. When toggled, NewsLeecher will write detailed information to the log window when checking downloads for spam. The option can be accessed from : Settings -> Downloads -> Spam Detection -> Detailed Spam Log... *: --------------------------------------------------------------- -- Larger Code Handling Changes -- ---------------------------- --------------------------------------------------------------- * 50% reduction in the size of the NewsLeecher install archive * Substantial faster NewsLeecher launch time on most computers * Overall performance improvements & smaller memory footprint --------------------------------------------------------------- *: To improve the efficiency of "SuperLeech", group indexing turn-around time for the "SuperLeech" search server has been lowered to ~30 seconds. This means that, in most cases, "SuperLeech" can now auto- matically leech newly posted article collections ( your favorite podcast series, etc. ), even *before* the NZB files for the article collections have been posted to the Usenet. *: The SuperLeech "Max Allowed Automatic Searches per Hour" limit has been raised from 6 to 15 for "Client Plus" packages. *: The SuperLeech "Max Allowed Automatic Searches per Hour" limit has been raised from 18 to 50 for "Ready To Go" packages. *: The SuperLeech "Turbo" feature is now available without any limits, for both "Client Plus" and "Ready To Go" package customers. *: NewsLeecher will now show various non-intrusive warnings when wanted articles cannot be leeched, due to low retention, take downs or other reasons. *: Updated the SSL library files used by NewsLeecher. *: Many smaller code and GUI improvements in NewsLeecher. !: Fixed bug where SuperLeech entries might hang for a long time, if the SuperSearch service wasn't responding properly to requests. !: Fixed rare bug where NewsLeecher would detect specific types of "RAR-in-RAR" files as spam, even though they are not spam. !: Fixed a small memory leak caused by deletion of "SuperLeech" tasks.

NewsLeecher 8.0 Beta 4

NewsLeecher 8.0 Beta 3

NewsLeecher 8.0 Beta 2

NewsLeecher 8.0 Beta 1

NewsLeecher 7.0 Final

NewsLeecher 7.0 Beta 15

NewsLeecher 7.0 Beta 14

NewsLeecher 7.0 Beta 13

NewsLeecher 7.0 Beta 12

NewsLeecher 7.0 Beta 11

NewsLeecher 7.0 Beta 10

NewsLeecher 7.0 Beta 9

NewsLeecher 7.0 Beta 8

NewsLeecher 7.0 Beta 7

NewsLeecher 7.0 Beta 6

NewsLeecher 7.0 Beta 5

NewsLeecher 7.0 Beta 4

NewsLeecher 7.0 Beta 3

NewsLeecher 7.0 Beta 2

NewsLeecher 7.0 Beta 1

NewsLeecher 6.5 Beta 6

NewsLeecher 6.5 Beta 5

NewsLeecher 6.5 Beta 4

NewsLeecher 6.5 Beta 3

NewsLeecher 6.5 Beta 2

NewsLeecher 6.5 Beta 1

NewsLeecher 6.3 Beta 2

NewsLeecher 6.3 Beta 1

NewsLeecher 6.2 Beta 1

NewsLeecher 6.0 Beta 2

NewsLeecher 6.0 Beta 1

NewsLeecher 5.2 Beta 2

NewsLeecher 5.2 Beta 1

NewsLeecher 5.1 Beta 1

NewsLeecher 5.0 Final

NewsLeecher 5.0 Beta 19

NewsLeecher 5.0 Beta 18

NewsLeecher 5.0 Beta 17

NewsLeecher 5.0 Beta 16

NewsLeecher 5.0 Beta 15

NewsLeecher 5.0 Beta 14

NewsLeecher 5.0 Beta 13

NewsLeecher 5.0 Beta 12

NewsLeecher 5.0 Beta 11

NewsLeecher 5.0 Beta 10

NewsLeecher 5.0 Beta 9

NewsLeecher 5.0 Beta 8

NewsLeecher 5.0 Beta 7

NewsLeecher 5.0 Beta 6

NewsLeecher 5.0 Beta 5

NewsLeecher 5.0 Beta 4

NewsLeecher 5.0 Beta 3

NewsLeecher 5.0 Beta 2

NewsLeecher 5.0 Beta 1

NewsLeecher 4.0 Final

NewsLeecher 4.0 Beta 24

NewsLeecher 4.0 Beta 23

NewsLeecher 4.0 Beta 22

NewsLeecher 4.0 Beta 21

NewsLeecher 4.0 Beta 20

NewsLeecher 4.0 Beta 19

NewsLeecher 4.0 Beta 18

NewsLeecher 4.0 Beta 17

NewsLeecher 4.0 Beta 16

NewsLeecher 4.0 Beta 15

NewsLeecher 4.0 Beta 14

NewsLeecher 4.0 Beta 13

NewsLeecher 4.0 Beta 12

NewsLeecher 4.0 Beta 11

NewsLeecher 4.0 Beta 10

NewsLeecher 4.0 Beta 9

NewsLeecher 4.0 Beta 8

NewsLeecher 4.0 Beta 7

NewsLeecher 4.0 Beta 6

NewsLeecher 4.0 Beta 5

NewsLeecher 4.0 Beta 4

NewsLeecher 4.0 Beta 3

NewsLeecher 4.0 Beta 2

NewsLeecher 4.0 Beta 1

NewsLeecher 3.95 Beta 3

NewsLeecher 3.95 Beta 2

NewsLeecher 3.95 Beta 1

NewsLeecher 3.91 Beta 2

NewsLeecher 3.91 Beta 1

NewsLeecher 3.9 Final

NewsLeecher 3.9 Beta 17

NewsLeecher 3.9 Beta 16

NewsLeecher 3.9 Beta 15

NewsLeecher 3.9 Beta 14

NewsLeecher 3.9 Beta 13

NewsLeecher 3.9 Beta 12

NewsLeecher 3.9 Beta 11

NewsLeecher 3.9 Beta 10

NewsLeecher 3.9 Beta 9

NewsLeecher 3.9 Beta 8

NewsLeecher 3.9 Beta 7

NewsLeecher 3.9 Beta 6

NewsLeecher 3.9 Beta 5

NewsLeecher 3.9 Beta 4

NewsLeecher 3.9 Beta 3

NewsLeecher 3.9 Beta 2

NewsLeecher 3.9 Beta 1

NewsLeecher 3.8 Final

NewsLeecher 3.8 Beta 9

NewsLeecher 3.8 Beta 8

NewsLeecher 3.8 Beta 7

NewsLeecher 3.8 Beta 6

NewsLeecher 3.8 Beta 5

NewsLeecher 3.8 Beta 4

NewsLeecher 3.8 Beta 3

NewsLeecher 3.8 Beta 2

NewsLeecher 3.8 Beta 1

NewsLeecher 3.7 Final

NewsLeecher 3.5 Final

NewsLeecher 3.5 Beta 10

NewsLeecher 3.5 Beta 9

NewsLeecher 3.5 Beta 8

NewsLeecher 3.5 Beta 7

NewsLeecher 3.5 Beta 6

NewsLeecher 3.5 Beta 5

NewsLeecher 3.5 Beta 4

NewsLeecher 3.5 Beta 3

NewsLeecher 3.5 Beta 2

NewsLeecher 3.5 Beta 1

NewsLeecher 3.0 Final

NewsLeecher 3.0 Beta 9

NewsLeecher 3.0 Beta 8

NewsLeecher 3.0 Beta 7

NewsLeecher 3.0 Beta 6

NewsLeecher 3.0 Beta 5

NewsLeecher 3.0 Beta 4

NewsLeecher 3.0 Beta 3

NewsLeecher 3.0 Beta 2

NewsLeecher 3.0 Beta 1

NewsLeecher 2.3 Final

NewsLeecher 2.3 Beta 6

NewsLeecher 2.3 Beta 5

NewsLeecher 2.3 Beta 4

NewsLeecher 2.3 Beta 2

NewsLeecher 2.3 Beta 3

NewsLeecher 2.3 Beta 1

NewsLeecher 2.1 Final

NewsLeecher 2.1 Beta 5

NewsLeecher 2.1 Beta 4

NewsLeecher 2.1 Beta 3

NewsLeecher 2.1 Beta 2

NewsLeecher 2.1 Beta 1

NewsLeecher 2.0 Final

NewsLeecher 2.0 Beta 13

NewsLeecher 2.0 Beta 12

NewsLeecher 2.0 Beta 11

NewsLeecher 2.0 Beta 10

NewsLeecher 2.0 Beta 9

NewsLeecher 2.0 Beta 8

NewsLeecher 2.0 Beta 7

NewsLeecher 2.0 Beta 6

NewsLeecher 2.0 Beta 5

NewsLeecher 2.0 Beta 4

NewsLeecher 2.0 Beta 3

NewsLeecher 2.0 Beta 2

NewsLeecher 2.0 Beta 1

NewsLeecher 1.0 Final

NewsLeecher 1.0 Beta 32

NewsLeecher 1.0 Beta 31

NewsLeecher 1.0 Beta 30

NewsLeecher 1.0 Beta 29

NewsLeecher 1.0 Beta 28

NewsLeecher 1.0 Beta 27

NewsLeecher 1.0 Beta 26

NewsLeecher 1.0 Beta 25

NewsLeecher 1.0 Beta 24

NewsLeecher 1.0 Beta 23

NewsLeecher 1.0 Beta 22

NewsLeecher 1.0 Beta 21

NewsLeecher 1.0 Beta 20

NewsLeecher 1.0 Beta 19

NewsLeecher 1.0 Beta 18

NewsLeecher 1.0 Beta 17

NewsLeecher 1.0 Beta 16

NewsLeecher 1.0 Beta 15

NewsLeecher 1.0 Beta 14

NewsLeecher 1.0 Beta 13

NewsLeecher 1.0 Beta 12

NewsLeecher 1.0 Beta 11

NewsLeecher 1.0 Beta 10

NewsLeecher 1.0 Beta 9

NewsLeecher 1.0 Beta 8

NewsLeecher 1.0 Beta 7

NewsLeecher 1.0 Beta 6

NewsLeecher 1.0 Beta 5

NewsLeecher 1.0 Beta 4

NewsLeecher 1.0 Beta 3

NewsLeecher 1.0 Beta 2

NewsLeecher 1.0 Beta 1

NewsLeecher 0.9 Beta 1

NewsLeecher 0.8 Beta 1

NewsLeecher 0.7 Beta 1

NewsLeecher 0.6 Beta 2

NewsLeecher 0.6 Beta 1

NewsLeecher 0.5 Beta 1

NewsLeecher 0.4 Beta 2

NewsLeecher 0.4 Beta 1

NewsLeecher 0.3 Beta 1

NewsLeecher 0.2 Beta 1

SuperSearch is currently running with a bit more than 4 years of article retention. But we are working hard to reach our goal of 10+ years retention. All 10+ years of Usenet article-data is in our storage, just waiting to be used to bump the SuperSearch retention.

The reason that retention is currently "only" at ~4 years, is that the amount of stuff posted to the Usenet is constantly rising. It requires more and more system resources to keep up, even though the index retention is kept constant. And not only that. We have also decided to start indexing subjects of text-groups and keep full index retention for audio and image (JPG, PNG, etc) groups. Those groups alone contain tens of millions of articles that we make fully searchable in true wildcard/substring (

Anyway. As mentioned above, we are working hard on improving the SuperSearch service at the moment. The service's backend-engine is being partly rewritten to improve performance and to make sure that the service is futureproof, by being able to keep up with the ever expanding Usenet retention demands.

We also use the code-rewrite opportunity to modulize the backend, so it gets a lot easier to add new functionality in the future.

While we cannot say for sure when exactly the job is done, we can say though, that it will be pretty soon. Things are progressing nicely and the most longhaired part of the optimization is done.

So all in all, good things to come soon :)

Copyright © 2020 NewsLeecher.com