NewsLeecher V8.0 Beta is now available!

Brand new UI | Tons of new/optimized functionality | *Much* more Usenet content available ( deobfuscation support ) | FREE Download
NEWS  LEECHER
News & Services Status Overview

Site News


February 7, 2020

Due to a bug in some new SuperSearch backend code, the SuperSearch service has been down for periods of time today. We have now reverted the code, so the service is back to working. Sorry for the inconvenience.

Optimization notice:
We are currently (still) working full time with optimizing the SuperSearch backend, to make searching, indexing and unscrambling faster - and, primarily, optimizations to bump the retention to 10+ (12+ actually) years for all indexed groups.

January 9, 2020

SuperSearch Retention Status Update:
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 ( *word* ) manner.

Note that it's really the "wildcard"-search capability, that makes it tricky to raise the SuperSearch search retention. If we simply used a genetic database approach (such as MySQL) to provide SuperSearch searching capabilities, we could easily bump retention to 10+ years and much much more if needed. But we really want to keep true wildcard searching available for our users and that's why it gets a lot harder to bump the retention, since generic databases don't implement true wildcard search capabilities. Everything has to be written from scratch and specifically tailored for the job that the SuperSearch service provides.

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 :)

Realtime Services Status Overview


Usenet Access Service


Current Status
OK

GEO Selector Server
OK
US Backend Servers
OK
European Backend Servers
OK
Binary Groups Retention
4,402.16 Days
Text Groups Retention
6,173.91 Days

SuperSearch Search Service


Current Status
OK

Service Usage Load
16.4%( Low )
Service Usage Graphs
Scroll to graphs
Service Article Retention
1,492.21 Days
Indexed Articles
665,133,711
Indexing Turn-Around Time
27 Seconds
Indexed Groups
14,005

NewsLeecher Software Application


Latest Released Version
8.0 Beta 4
Days Since Latest Release
161.72 Days
Avg. Days Between Releases
31.13 Days
Number of Final Releases
12
Number of Beta Releases
192

Additional NewsLeecher Status


Current Status
OK

License Key Generator Status
OK
Main Website Status
OK
Forums Website Status
OK
NewsLeecher Mail Server Status
OK

SuperSearch & SuperLeech Usage Graphs


Graphs Are Updated Hourly

Usage load over the last 24 hours time ...

Usage load over the last 3 days time ...

Usage load over the last 7 days time ...

Usage load over the last 14 days time ...

February 7, 2020

Due to a bug in some new SuperSearch backend code, the SuperSearch service has been down for periods of time today. We have now reverted the code, so the service is back to working. Sorry for the inconvenience.

Optimization notice:
We are currently (still) working full time with optimizing the SuperSearch backend, to make searching, indexing and unscrambling faster - and, primarily, optimizations to bump the retention to 10+ (12+ actually) years for all indexed groups.

January 9, 2020

SuperSearch Retention Status Update:
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 ( *word* ) manner.

Note that it's really the "wildcard"-search capability, that makes it tricky to raise the SuperSearch search retention. If we simply used a genetic database approach (such as MySQL) to provide SuperSearch searching capabilities, we could easily bump retention to 10+ years and much much more if needed. But we really want to keep true wildcard searching available for our users and that's why it gets a lot harder to bump the retention, since generic databases don't implement true wildcard search capabilities. Everything has to be written from scratch and specifically tailored for the job that the SuperSearch service provides.

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 :)

Site Navigation

Copyright © 2020 NewsLeecher.com