The server is working without problems, probably I will work on the client, I'll check older requests and bug reports, so i'll take a break from indexing as the main topic after about three months of work on it.
As to the server most users are satisfied with the current retention, it won't be a problem to increase it when needed.
was: the next release (pre 1.16)
i am not sure if i put this message on the right place, so maybe you must place it somewhere else.
maybe include an option to let usenet explorer save files over more disks.
for example that usenet explorer sees that it reaches the end of the disk capacity and changes to another disc. Of course this other disc should be a disc that the user fills in the settings of ue. So ue should have a list of available disks or disc partitions or folders on other disc partitions etc.
Now usenet explorer only notifies the space left on the disc on which it is installed. And maybe more relevant is the space that ue knows it has available to store the downloaded files.
so usenet explorer should show the space that is left for the files.
maybe include an option to let usenet explorer save files over more disks.
for example that usenet explorer sees that it reaches the end of the disk capacity and changes to another disc. Of course this other disc should be a disc that the user fills in the settings of ue. So ue should have a list of available disks or disc partitions or folders on other disc partitions etc.
Now usenet explorer only notifies the space left on the disc on which it is installed. And maybe more relevant is the space that ue knows it has available to store the downloaded files.
so usenet explorer should show the space that is left for the files.
if the program runs out of space it stops saving you can free space or change the destination drive. the database partition is additionally protected by low disk space detection.
but in fact now i started to check older topics which accumulated while i was working on indexing including bug reports, it is like a standard software maintenance.
afterwards it is likely i'll make the v1.2 release and switch to another large topic, since i want to exploit the potential of the ue framework, it hasn't been fully used yet.
but in fact now i started to check older topics which accumulated while i was working on indexing including bug reports, it is like a standard software maintenance.
afterwards it is likely i'll make the v1.2 release and switch to another large topic, since i want to exploit the potential of the ue framework, it hasn't been fully used yet.
yes, technically there is now no problem to save attchments.
in first versions it blocked saving alltogether when the database drive was full, thus if there was only database and it took all the partition it wasn't possible to save without deleting some bodies first. but then i fixed it so saving in such a case is only suspended on tasks which go to the database drive, at least you can always save somehow.
but now i want to develop further methods i used in the past for boosting reliability (i like to play with statistical data) so several days will go for that purpose.
in first versions it blocked saving alltogether when the database drive was full, thus if there was only database and it took all the partition it wasn't possible to save without deleting some bodies first. but then i fixed it so saving in such a case is only suspended on tasks which go to the database drive, at least you can always save somehow.
but now i want to develop further methods i used in the past for boosting reliability (i like to play with statistical data) so several days will go for that purpose.