#acl All:read contribGroup:read,write <> = sn = == Availability and IPv6 support == || '''Name''' || '''IPv6 support''' || '''Supported operating systems''' || || [[http://infa.abo.fi/~patrik/sn/|sn]] || included via uscpi tcpserver || Linux, ? || == Description == sn is a small news system for small sites serving perhaps a few dozen newsgroups, and with a slow connection to the internet. It is similar to Leafnode. The target user is a home or SOHO with a single modem connection to the Internet, maybe running IP masq or similar, and serving a few workstations. sn is fast. The news fetcher implements command pipelining and parallel fetches, so high modem latency doesn't cost you. (You can also throttle sn down, if it's too fast). sn is flexible. You can subscribe to newsgroups on several upstream sites, and you can create local newsgroups that are not propagated upstream. sn can make mailing lists look like newsgroups transparently. sn is non-intrusive. It has no configuration files, only control files with simple semantics, so it's suited to being run in an automated fashion. sn is small. It batches 10 (default) articles per file, so conserving inodes and reducing disk block fragments. sn can also compress the article bodies. It aliases cross posts rather than making separate copies. It does not maintain a bulky overview database; instead it gets overview information directly from the articles. Spool metadata is 5% to 10% of the total spool size, even with compression. You don't need to build a separate file system just to spool news. sn doesn't have to be set up for the system. You can use it privately, and your users can maintain their own news spool without building sn. == Comments == you need uscpi tcpserver from http://www.fefe.de/ucspi/ == Usage information == == Categories == CategoryApps, CategoryAppsnews == Source of information == Bieringer IPv6 pages