Actually, "-" is an ok character for both host names/URLs and file names as well as inside Helma, so I see no good reason why not to allow it.

It feels strange to writewithoutspaces.

henso opened a topic that needs a solution: should antville.org allow private weblogs? since the current way (let them exist, but list them in the recent-update-list on antville.org's frontpage so that we get a clue about their "activity") is not what i would call a "solution", we have to find a new one.

regarding antville.org's policy, i'd propose private weblogs should not be allowed anymore (because nobody of us - meaning the maintainers of antville.org - has the time/nerve to observe them, and the current version of antville is also not helpful at all in this case).

so, the question is: should the application antville keep the feature or not? the simplest way would be to remove the "private weblog"-feature in antville(-code) and delete all currently existing private weblogs (they'll have to find a new home).

or should we implement a "feature switch" in antville, so that it would be up to the maintainers of antville-installations if private weblogs are allowed or not - much like "allowGoodies" works now (in case of antville.org, it would be disabled).

The code hadn't been adapted to the new parameter requirements in storymgr/evalNewStory().

good morning.

today i retouched the files of an rss aggregator i started to create with helma last year. goal is to put its functionality into antville.

benefit is to provide access to news, magazines and weblogs located outside of antville from antville's core functionality (ie. an antville weblog).

currently, the aggregator reads periodically reads user-added rss files and turns them into stories (ie. not antville stories, the rss application is not related to a weblog infrastructure, yet).

but: wouldn't it be pretty intersting to turn the rss feeds into antville weblogs and each rss channel item into one of such an rss weblog's story?

the pretty result of such an approach would be that i don't have to make any distinctions between user-driven and rss-driven stories. this means i also have to provide only one way to display a collection of stories, be it from one weblog or from a bunch of (e.g. topic-selected) weblogs, and be it a user-driven weblog or one derived from an rss feed.

the bad thing, however, could be that suddenly there are types of a "ghost" weblog here at antville containing all the work somebody helds at another place (the origin of the rss feed), too.

i am sure this could be avoided by implementing the rss channel prototype as an extention from the standard antville weblog prototype and the rss story prototype as another one from the text prototype (just as the story and comment prototypes are already). the only difference would be then that these rss stories are not visible to the public... i am not sure about this that's why i kindly request your appreciated opinions and comments.

(and feel free to ask me anything if i should have been not very clear in the first paragraphs.)

while i transformed my former blogger weblog into an antville one, i made some observations (and actually some tweaking from these observations) about some antville macros and structures. please read more inside.

hmm....lets see if this works, shall we?

i created a destination for downloading antville (www.antville.org) on this server, plus i put a first version of the antville-license (also in CVS now) together with a short description of how to get antville into <about antville>. please read and feel free to comment.