(Reposted from the "freenet" frost board.)
Maybe I'm too tired but I just had an idea how to get rid of Frost. ;)
(Don't get me wrong, Frost works pretty good but I'm more used to read
something news-like with My Favourtie News Reader. I also like threads.
And scoring. And the fonts I use everywhere on my system. :)
The architecture looks like this:
In the beginning, there is Alice setting up an FNTP (Freenet News
Transfer Protocol :) backend thingy using a backend thingy manager GUI.
She defines some things, like the name of the server, her (optional)
contact data, list of imported servers. She also sets up a couple of
newsgroups she likes to offer. When she is done she announces the
address of her server somewhere.
Now Bob wants to read news from Alice's server. So Bob starts up a local
daemon, his favourite news reader, and a FNTP server manager. The
latter is a small GUI program (or web-frontend) where he enters the
address of Alice's server. The server manager talks to the local daemon
and tells it to contact Alice's server. The local daemon then starts by
getting the groups list. Meanwhile, Bob uses like favourite news reader
to connect to his local daemon which offers him the groups Alice offers
(if it has fetched them already). He subscribes to the groups he wants,
gets the headers and bodies for message, reads them, answers to them,
and does all the other funny things a news reading person does.
Of course, Bob is free to add more than one server in his FNTP server
manager. (One could use different port numbers so that the servers can
easily be told apart when using the news reader.)
In normal usenet, if you want to add a board you have to kick off a
lengthy discussion with lots of admins. In FNTP, if Bob wants to add a
board to Alice's server, he uses his server manager GUI to send a
suggestion of the board to Alice. Alice receives this using her backend
thingy manager GUI and can deny or approve the request for the new
board. Local daemons that are connected to her backend can then pick up
the news groups and show it to their users when they log in.
Alice has the option of having her backend import groups and messages
from other backends. This way some people can create meta-servers that
coalesce any number of differently themed servers.
Also, Alice can decide to have some groups moderated so that if a new
message is posted from some Bob she has to approve or deny this
message, manually or via some filters based on poster ID. She also has
the ability to "outsource" the task of moderation to Charlie. This will
probably work with some complex key signing/encryption theme that I
haven't thought about yet. :)
One other thing I'd like to add in is automatic signing of every posted
message with a GnuPG key whose public key is also automatically
attached to the message to allow simple integration into news readers
that support that type of security (like KMail or Thunderbird+Enigma
do).
Okay, I think those are the ideas I have until now. Do you have
questions? Do you have anything to add? Do you have ideas about
implementation details? Do you want to tell me how stupid I am?
Whatever it is, go right ahead. :)
So, off to work,
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20060724/19c8dbb3/attachment.pgp>
