Mercurial > noffle

view FAQ.html @ 38:8e972daaeab9 noffle

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[svn] Applied patch from Jim Hague: - Forget cached group info when group database closed. - Added list of 'forbidden' newsgroup specs. - Fixed problem with article numbering if the overview file empties. - Changed %i to %d in sscanfs (%i interprets leading zeros as octal numbers) - New groups now always start numbering at article 1. - Record newsgroup posting status. Enforce it at posting time. Added --modify - Added group deletion. - Added wildmat code taken from INN
author enz
date Fri, 05 May 2000 08:23:15 +0100
parents e9fdb0f66563
children
line wrap: on
line source

<html>

<head>
<title>NOFFLE FAQ</title>
</head>

<body bgcolor=white>
<p>

<center>
<h1>NOFFLE FAQ</h1>
</center>

<p>
<hr>
<p>

<b>Q:</b> What is the difference between NOFFLE and leafnode?
<p>
<b>A:</b> NOFFLE uses less resources (disk space and bandwidth). Downloading
groups in overview mode is several times faster, because it uses the XOVER
command instead of HEAD. In addition, there is the quasi-transparent mode,
when online, which allows to browse through groups and cache everything
without subscribing.<br>
NOFFLE is GPLed, leafnode isn't. 

<p>
<hr>
<p>

<b>Q:</b> I subscribe to groups, but get a "Retreiving failed"
message for every requested article.
<p>
<b>A:</b> Some news server do not allow retrieving articles by message-ID.
You cannot use NOFFLE together with these servers presently.

<p>
<hr>
<p>

<b>Q:</b> I changed the server in the config files, but the
new groups do not appear.
<p>
<b>A:</b> You should run <code>noffle --query groups</code> again. If you
want all old group information deleted, you should remove the file
data/groupinfo.gdbm in the spool directory before.

<p>
<hr>
<p>

<b>Q:</b> The Emacs news reader GNUS hangs while getting active list
from server.
<p>
<b>A:</b> This is a known phenomena and I believe that it is a bug with
GNUS, because the log files show correct handling of client commands by
noffle.
                                                                                
</body>
</html>