Free newsgroup software for linux

NewsBro project is a web application providing usenet news service. It provides support for multiple users accessing multiple news groups via multiple news servers.
Main features:
- web-based Usenet access
- full-featured news reader
- multi-user access with individual profiles
- one click filtered access to all images within a newsgroup
- multi-server binary file support
- XFace support
- yEnc decoder
- stand-alone and Java servlet versions
- News RC File
- Header and article caching
- NZB support
- XPAT threading
- Binary file harvesting
- Watch List for monitoring followups
- RSS feed for each group
- Configurable threads list

Newsd is a standalone local NNTP news server for private newsgroup serving on a single server.
It is useful for serving private newsgroup(s) to an intranet or the Internet and can act as a simple mail gateway, however it does not interface with other news servers and cannot manage distributed news feeds, i.e. Usenet news.
Newsd is available under the terms of the GNU General Public License. The Newsd source code should compile on any POSIX-compliant operating system. Binaries are provided for Linux and MacOS X.
Enhancements:
- Important fix to multiline headers being split during header reordering
- STR#15: Path: now maintained and passed through mail gateway
- STR#16: Mailgateway: "From" field now renamed to "X-Original-From:"

newslite is a UNIX/LINUX command line tool to download from newsgroup and decode multipart and monopart yENC and UU (Unix-to-Unix) encoded files.
Main features:
- threads XOVER command for faster group message header retrieval
- threads file download for faster download
- builds full list of groups hosted by the server
- resumes download session in case of connection loss program interruption
- makes use of configuration file to simplify user command interface
- builds "title" and "file" lists from article headers for quicker group content analysis
- decodes yEnc and UU multi and mono-part encoded files
- supports news server authentication
- supports NZB file processing (check the newzbin site for further information)
- allows connection to news server through any TCP port (i.e. not only using NNTP 119)
Enhancements:
- This release adds a group Search option.
- The MAC binary is now universal (PPC and Intel).

WWW::Google::Groups is a Perl module for Google Groups Agent.

BROWSING

use WWW::Google::Groups;

$agent = new WWW::Google::Groups
(
server => groups.google.com,
proxy => my.proxy.server:port,
);


$group = $agent->select_group(comp.lang.perl.misc);

$group->starting_thread(0); # Set the first thread to fetch
# Default starting thread is 0

while( $thread = $group->next_thread() ){
while( $article = $thread->next_article() ){

# the returned $article is an Email::Simple object
# See Email::Simple for its methods

print join q/ /, $thread->title, header(From).>, $/;
}
}
If you push raw to the argument stack of $thread->next_article(), it will return the raw format of messages.
while( $thread = $group->next_thread() ){
while( $article = $thread->next_article(raw) ){
print $article;
}
}
Even, you can use this more powerful method. It will try to mirror the whole newsgroup and save the messages to a Unix mbox.
$agent->save2mbox(
group => comp.lang.perl.misc,
starting_thread => 0,
max_article_count => 10000,
max_thread_count => 1000,
target_mbox => perl.misc.mbox,
);

SRCP is a TCP/IP Protocol to cover all aspects of model railroading. It is ascii text based and follows a strict command-response schema. In the world of SRCP the server is the interface to the model railway system.
Any client connects to the server and recieves information about the state of any component (including the server) and sends commands to change the state of any component. Thus SRCP is fully multiuser. To prevent conflicts, a component can be locked by one client session.
SRCP means Simple Railroad Command Protocol. It is an IP based protocol. It covers all aspects of model railroading. srcpd project implements a client-server architecture.
SRCP defines an abstract layer above the model railroad system. If covers the differences between DCC or MarklinMotorola or any other system. A client developer does not need to know, which type of signalling is used. Even if a complete new system comes up: once a SRCP server implements it, any SRCP client can be used without any change.
SRCP consists of command words and devices, on which the commands operate. Command words are SET, GET, WAIT, VERIFY, RESET, INIT and TERM. The most important devices are locomotive decoders (GL== generic loco), impulse decoders (GA == generic accessoire) and feed back sensors. To address decoder programming so called Service mode devices are defined.
All components are structured in busses, which basically bundle components which are accessible through a shared device (e.g. a central unit). These busses will also be used to segment the adress space. One basic feature of SRCP is that it never changes the hardware adress. E.g. can the NMRA "short" addresses and the "long" addresses be structured into two independent busses. It is the responsibility of the server developer, to define the the bus structure well. A client developer has to take care, that the address of any component contains two elements.
Not all components does exists on all systems. To get initial information, the server can inform the client about all devices it knows about. Some functionality can even be emulated by the server, if the target does not support the requested feature (e.g. get current speed: many railroad systems do not support this operation).
Another nice feature, which is can be used is a central time source. SRCP contains a time "device", which keeps all clients with a current model time. This time can run at any ratio to the real time: 6 real time minutes can be 1 model hour.
SRCP has evolved over time. The first usable revision, which is outdated by now is called 0.7.3. It works well and a lot of program still use it. For all software we encourage to use the current version 0.8.2, which is stable for more than a year. The most recent version is called 0.8.3-wip, which contains a few enhancements. They are not yet formally correct and may contain errors or can be changed in the future.
Future Versions of SRCP will keep compatability with the current 0.8 specification. A client can request a special SRCP version during the initial handshake.
The discussion around SRCP runs in the German newsgroup de.rec.modelle.bahn.
Enhancements:
- This release adds basic loconet support, provides enhancements for Selectrix and LI100, and includes internal changes for better support of Linux 2.6 and 64-bit architectures.
- From the SRCP 0.8.3 the SET FB feature was implemented.
- This is most useful for the loopback bus, as others may suffer from hardware support.

KNewz project is a binary newsgroup client for KDE4. I wrote it because there is no one client out there that does what I want it to. Planned features include automatic PAR2 checking (via kpart, whee), automatic unpacking of downloaded files, System tray support (trivial I know), DBUS support, automatic queue save and restore upon shutdown/startup. Feel free to request more.
Enhancements:
- Development has been on hold for the summer vacation :) KDE Beta 1 has just come out however, so I made the code compatible with it. I hadnt been developing it lately since the KDE API was constantly in flux, and I got sick of adding new features only to have my code not compiling with the next SVN revision because the API had been changed. However, the API has been frozen now so Ill be developing this actively now again.
- The good news is that I have been using this exclusively to download my binaries, and I have found and fixed lot of bugs. A few remain though, and will be fixed for the 0.1 release. Queue saving and editing features will be introduced in the 0.2 release, and the connection code will be rewritten.

GoodProfOrNot is a database and web system for organizing, interpreting, and presenting course survey results.
GoodProfOrNot project is designed to show ratings of instructors (professors and student instructors) and classes.
The project is implemented in Python (see below for rationale). The back-end uses any SQLObject-compatible database, such as MySQL, PostgreSQL, SQLite.
The front-end outputs raw hand-designed/coded HTML and CSS. Output can either be dynamically generated using the CGI front-end (with caching and mod_python/FastCGI support) or pre-generated as static HTML.
Python allows rapid prototyping and implementation: to add the "newsgroup" field to the system only took 15 minutes to update the database schema and HTML front-end, and 10 minutes to write a program to link all the ucb.class.(cs|ee)* newsgroups.
This course survey system started as a final project for a Python class taught by student instructor Ka-Ping Yee. Its primary goal was to replace an old system used by Eta Kappa Nu at UC Berkeleys EECS course survey system. It has since become very successful and other schools use it.
Enhancements:
- Fix parse error when user enters search query of e.g. "CS C191".
- Bug reported by Ramesh Sridharan

ngbatch project is a newsgroup/rmgroups batcher for INN.

SYNOPSIS

< ngbatch -n > < group > [ < flag > [ < creator > ] ]

< ngbatch -r > < group >

< ngbatch -e > [ < -D > ] [ < -w > < days > ] [ < -h > < days > ]

This program executes newgroup and rmgroup controls in a delayed way, to help against newgroup/rmgroup wars. The idea is that (a) rmgroups are remembered for some time, and (b) rmgroups get priority over newgroups, so that a newgroup will be ignored if a rmgroup for this group (from a trusted issuer) has already arrived. A newgroup is executed only after a wait period, in case it gets rmgrouped soon.

Each newgroup/rmgroup control message is written into a batch file. A cron job collects commands from this batch file and executes only those newgroups for which no rmgroup was received.

Setting Up

Change your control scripts for newgroup and rmgroup so that they call B< ngbatch > with the appropriate parameters instead of B< ctlinnd > (you probably should make that depend on hierarchies). Make sure that only trusted rmgroupers are active in the I< control.ctl > file.

Run < ngbatch -e > periodically from crontab.

OPTIONS

< -n > < group > [ < flag > [ < creator > ] ]

Batch up a newgroup control for < group >. < flag > defaults to "y", < creator > defaults to nothing.

< -r > < group >

Batch up and execute a rmgroup control for < group >.

< -e >

Execute a batch run: for all batched newgroup commands, check if the wait time has elapsed. If yes, execute the newgroup command only if no rmgroup for the same group was batched. Rewrite the batch file with the commands still to be remembered.

< -D >

Show the commands on standard output instead of executing < ctlinnd >.

< -w> < days >

Set the newgroup wait time to < days > (default 3).

< -h > < days >

Set the rmgroup remember time to < days > (default 30).