[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
RE: best practice for providing newsfeeds ?
- To: "Dare Obasanjo" <dareo@m...>,<bob@w...>,"Michael Champion" <mc@x...>,"XML DEV" <xml-dev@l...>
- Subject: RE: best practice for providing newsfeeds ?
- From: "Joshua Allen" <joshuaa@m...>
- Date: Tue, 3 Feb 2004 10:31:54 -0800
- Thread-index: AcPqdWkuTBaqcxC8TEGozT/1AFE4DgAAICKgAADG5F8AApcv0A==
- Thread-topic: best practice for providing newsfeeds ?
Title: RE: best practice for providing newsfeeds ?
By people I meant tools. I get a few
hundred posts a day that show up as “new” when they are old, simply
because people have crummy tools that reset the pubDate on *all* posts to be whatever date the feed
gets updated. I also am pretty sure that these people have no idea that their
tools are doing this, and don’t lose any sleep over it. In other words, normal
people don’t care about what date gets inserted, and only the techies
argue about it. I don’t believe that the call for multiple date fields
is being driven by significant end-user demand. I think that’s total
bull.
From: Dare Obasanjo
Sent: Tuesday, February 03, 2004
9:13 AM
To: Joshua Allen; bob@w...; 'Michael Champion'; 'XML DEV'
Subject: RE: best
practice for providing newsfeeds ?
I disagree. Most tools insert this
date automatically. I'd be very suspicious of a tool that allowed users to
directly edit the posting date of an entry, let alone edit the original +
posting date. I agree with Bob that having a published + updated date would be
useful.
Blessed are the meek for they shall inherit the Earth, minus
40% inheritance tax.
From: Joshua Allen
Sent: Tue 2/3/2004 9:02 AM
To: bob@w...; Dare Obasanjo; 'Michael Champion'; 'XML DEV'
Subject: RE: best
practice for providing newsfeeds ?
> date
that it was last modified. So, users get entries that appear to
> be "old" even when
they are "new." This confuses them. The issue here
> has *nothing* to do with data
format -- it is a question of semantics,
My
experience shows exactly the opposite; people report "new" when
actually a post is old. But in any case, I fail to see how adding another
field will stop people from putting the wrong dates in those fields -- the
semantics of "pubDate" are remarkably clear, and people still screw
it up. I would bet that in 99% of cases, people screw it up because they
don't know better, NOT because "pubDate is the only field available and I
really, really, want to store the last-update date in the field".
Solving
user ignorance by adding more features is not very smart.
|
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|