Currently DFeed requires an NNTP server as backend but duplicates it's message database. It would be far more efficient make DFeed an independent NNTP server and host content rather than duplicating it. This would save a lot of disk-space and probably make using NNTP clients faster, assuming that DFeed:s database is faster.
Another solution of course would be to have an external NNTP server but with a shared database which probably could be done by modifying an existing NNTP server to use a database that is acceptable to DFeed.
Currently DFeed requires an NNTP server as backend but duplicates it's message database. It would be far more efficient make DFeed an independent NNTP server and host content rather than duplicating it. This would save a lot of disk-space and probably make using NNTP clients faster, assuming that DFeed:s database is faster.
Another solution of course would be to have an external NNTP server but with a shared database which probably could be done by modifying an existing NNTP server to use a database that is acceptable to DFeed.