Revision r1.6 - 08 Oct 2002 - 17:33 GMT - TWikiGuest[This idea is under development, comments are welcome on this page.]
- One Radio user appoints him or herself the group weblog maintainer.
- Contributors post weblog entries to a special category on their own weblog sites.
- Contributors make their XML weblogArchives available (at least of the group category)
- Maintainer's Radio subscribes to contributors' special category RSS
- Maintainer's Radio pulls down and aggregates contributors' XML content
- Maintainer renders contributors' content in weblog's theme
- Maintainer's Radio upstreams the content to the group weblog
- Could allow non-Radio weblog authors to participate
- No alterations of entries posted by contributors after aggregation?
One problem with using RSS is the clients won't be able to publish immediately to the group blog. New items from clients will only appear when the maintainer's aggregator runs, presumably hourly, and reads their RSSes. The Radio DG discussion mentioned the Blogger API, and it (or the Weblog API from weblog-devel) would remove the aggregator dependence--but require a client-side Tool. -- MarkPaschal - 06 Mar 2002 RE: lack of immediacy -- This is true. Just trying to think of a way to enable this group weblog assuming there are no smarts on the server and that no members of the group can connect to each other. Say everyone is behind separate firewalls, and the webserver is static content and FTP-only. No CGIs or other web apps. The only way to communicate in this scenario (as far as I have imagined so far), is to drop files in known locations and pick them up periodically. Thus, the notion of RSS (or some other format) aggregation. -- LesOrchard - 07 Mar 2002
- Weblog data is contained in a guest database weblogData.root
- Guest databases can be updated from remote sources
- Could multiple users 'subscribe' to updates to the same weblogData.root?
- Could multiple users upstream updated to a shared weblogData.root?
- Using the upstream mechanism keeps the sharing mechanism simple.
- Version control of the weblogData.root is not so simple.
- Concurrency, locking?
- Contributors' Radio installations each take turns uploading HTML rendered content to manage the website.
- Assuming everyone uses the same weblog skin
- Security? Not much at all, in this scenario. How to handle it?
- Coarse barriers: allow only collaborators access to shared weblogData.root and upstreaming, assume they'll all behave?
- See: Wiki:WhyWikiWorks
- Weblog management system would need to be heavily reworked to support this.
- Would xmlstoragesystem.com be a better model for this? Available, but not braindead simple.
- Biggest benefit is that no one group member is the maintainer, any group member can modify the weblog
- A downside is that it would be a lock-in to Radio