Add Comment

You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog Aggregating external articles


Re: Aggregating external articles
Posted by dkg (216.254.xx.xx) on Mon 12 Mar 2007 at 19:59
Those are good ideas, Julien. And i don't think you're making excuses, we're just hashing out a way that things might work.

I agree with you that being optimistic and having freer policies (with rollback coupled with auditable historical trails) is a better way to go in general (interesting thoughts by Joey Hess about this). And i definitely think that being able to submit your own specific articles (hosted elsewhere) for inclusion in d-a.org is a really good idea: no one wants to maintain two copies of a work, and an author's work really does belong on their own web presence, even if it also belongs on d-a.org.

One model that just occurred to me is to have yawns cache a copy of the syndicated article, and check regularly (whatever that means) for updates via HTTP against the original source. If there actually are updates, the updates themselves are treated as edits pending moderation on d-a.org, and wouldn't be published on d-a.org until they were reviewed by the site admin.

Things that would be necessary to make this work conveniently:

  • good publishing policy by the upstream author:
    • don't offer dynamic content for syndication.
    • don't include your site's users' comments in the syndicated text
    • choose a real, permanent URL
    • make sure your web server is publishing appropriate changed-on headers
  • convenient diff markup in yawns for the site editor to review changes to an article pulled from a syndicated source
  • clear site policy about what's allowed and not allowed, to make decisions about accepting/rejecting edits easier.
  • clear upstream policy about syndication permissions (e.g. this article may be republished freely by d-a.org, when d-a.org becomes aware of changes to this article, d-a.org {may,may not} continue to cache older revisions if the new revision is unacceptable, etc): maybe this could be done at syndicated article submission time?

This is all from the point of view of users submitting specific articles for inclusion on d-a.org, of course.

Users submitting an article stream for inclusion is a whole other prospective can of worms.


Username:Anonymous
Title:
Your Comment:

Posting Format:

 

Inappropriate comments will be removed.

Some help on entry formatting is available

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search