On Fri, 29 Dec 2000, Brandon wrote:
> Mark:
> > Yes, and MSKs make it trivial to regularly insert your site. Without MSKs
> > this was a valid point, because it was not feasible to insert 10,000
> > redirects every hour. But with MSKs, inserting the updated version is so
> > trivial you could do it every minute, and as a bonus, you get an
> > easily-accessible complete archive of your previous posts, perfect for
> > news sites or moderated discussion groups where content is updated often.
>
> I've already addressed in an e-mail yesterday why there are disadvantages
> to inserting even one small file every minute. To summarize, you need
> uninterrupted Internet access, which not everyone has, and it makes it
> easier to attack a publisher because you can track them one hop at a time
> instead of requiring surviellance of the entire network.
>
> > Moderated discussion groups would be a good project for EOF.
>
> Yes, they're on our list.
>
> > Is anyone writing a set of daemons like this, or should I go for it?
>
> We're working on similar things except that they interface that I'm
> implementing lets you use your normal mail or news client and all of that
> stuff happens in the background. If you'd like to write a library for
> doing such things then it would be very much appreciated. Mr. Bad has
> started on a library for doing mail. It's in the EOF CVS. (freenetmail)
I'm halfway there. The same daemon handles inserts and requests. It reads
a config file with fieldsets like
insert.forum1.spool=/var/spool/mail/root //mail spool to watch
insert.forum1.name=My Forum's Name Here //human name of forum
insert.forum1.webarchive=50 // number of messages on each web archive page
insert.forum1.webrate=6 // insert new webarchive every x times
insert.forum1.privatekey=freenet:SSK@asdf/list // root updatable SSK redirect
insert.forum1.baseline=20000101000000 // updating baseline
insert.forum1.increment=600 // updating increment (seconds)
insert.forum1.preempt=60 // how many seconds in advance to insert the data
where forum1 is just an arbitrary forum ID. It spawns an insert thread for
each one it sees. The thread watches the specified mail spool. Every
/increment/ seconds (minus the /preempt/), it inserts the latest messages
in raw mailbox format. Then, if it's time to insert a web archive, it
pushes them into the web archive FIFO and inserts it as HTML (if enabled).
Finally, a mapfile is inserted containing these two keys under the updated
key. So you get a complete browser-readable archive that can be redirected
to from a KSK MSK like freenet:freenet-dev// and a realtime mailfeed for
subscribers. In a couple days, the process of creating a forum and adding
it to the config file will be automated. Also, you'll be able to subscribe
to an existing forum automatically.
I still haven't decided how robust the filtering has to be for
insertion. I think the ability to filter based on a From: header and/or a
subject string ("[freenet-dev]", etc.) should be sufficient. In its
present form this thing is intended to allow free-as-in-price mailing list
distribution. Once we find a reasonable solution to the
in-Freenet-submission problem, it'll allow free-as-in-speech mailing
lists, albeit with a moderator and central inserter. But you'd think
mailing list software could be easily configured to send the mailing list
to a local spool for insertion, so filtering isn't a big deal there.
Brandon, why is SimplifiedClient printing the size of each message it
inserts? I don't see anything obvious. It fucks with my logging.
Also I found out a few days ago that getData doesn't work, but getMetaData
does. The main() in SimplifiedClient fails unless I change getData to
getMetaData, and then it works fine. Weird.
--
Mark Roberts
[EMAIL PROTECTED]
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
