I read setiathome RSS News through Safari on MacOSX10.4.4.

Presently there are nine(9) entries in the News.

Opening Console (/Applications/Utility/Console.app), I notice the nine messages in the system console window:
~~~~~~~~
2006-01-27 07:36:07.980 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Thu, 15 Dec 2005'
2006-01-27 07:36:07.982 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Thu, 15 Dec 2005'
2006-01-27 07:36:07.984 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Fri, 23 Dec 2005'
2006-01-27 07:36:07.986 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Thu, 05 Jan 2006'
2006-01-27 07:36:07.987 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Thu, 05 Jan 2006'
2006-01-27 07:36:07.989 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Fri, 13 Jan 2006'
2006-01-27 07:36:07.990 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Sat, 14 Jan 2006'
2006-01-27 07:36:07.991 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Mon, 16 Jan 2006'
2006-01-27 07:36:07.993 SyndicationAgent[24561] WARNING: BestCalendarDateFromString - can't interpret: 'Fri, 20 Jan 2006'
~~~~~~~

These messages appear every 30 minutes, which is identical to the browser setting interval; these message appear only while the browser is up.

I suppose these messages are produced in accordance with the setiathome RSS News.

I wish to get rid of these garbages out of my system console, so that I won't miss other impotant messages.

---

It works here. It must be Safari. I'm using FeedDemon 1.6 RC2.
Try to clear the cache or reset the feed. Maybe delete the feed and create it again. You can also try this Feed Validator.

Dear setiathome and all participants;

Please accept my apology.

Setiathome seems stopped casting rss.

I wasn't careful enough;
I had another symptom with safari's rss reader.

I'll bring this issue to Apple's board.

Also, Thanks to Prognatus.
I flipped back to old RSS reader.

Mak Fuego

---

I tried 'Feed Validater' and got the report:

~~~~~~
Sorry

This feed does not validate.

line 18, column 19: guid must be a full URL, unless isPermaLink attribute is false (9 occurrences) [help]

<guid>0</guid>
^
line 24, column 37: pubDate must be an RFC-822 date-time (9 occurrences) [help]

<pubDate>Fri, 20 Jan 2006</pubDate>
^
~~~~~~~

It says pubDate of setiathome's feed doesn't conform.

Again, my fault.

Oh! my god!

---

It says pubDate of setiathome's feed doesn't conform.

Again, my fault.

If the feed doesn't validate, it's not your fault (or Safari). Please submit a bug report of this.

RSS feed works perfectly fine here on my reader

---

Join us in Chat (see the forum) Click the Sig


Join UBT

I'm now thinking another aspect: Apple-Safari may be violating the copywright of setiathome.

Let me suppose that the pubDate field of setiathome feed has only date, doesn't contain time.
If it is the case, however, Safari shows up both date and time; an arbitrary character string for time is apended by Apple.

The news from setiathome is in general of the day, not a fact at a sharp instance.

This is the issue raised by the protocol and its interpretation.
Protocol should be written so as not to raise such doubt.

I also like to point out that a feeder may say that
a browser should show exactly in the sequence as issued; do not reorder.

Even in the cosmology world, human-principle is taking the important role.
Why a protocol can't be humane?

---

I posted this and another by mistake. How can I remove?

---

---

This is the issue raised by the protocol and its interpretation.
Protocol should be written so as not to raise such doubt.

it's not a protocol issue at all, the spec is quite clear that dates and times should be ISO compliant

SETI doesn't use ISO dates, so SETI is publishing an invalid RSS feed, SETI is at fault

and it's not a protocol anyway, it's a data format

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Engines

In general, with the character string representation of time (9 fields), there is such an understanding that fields can be dropped from right to left. This is a kind of defacto standard, this is always meant implicitly anywhere it is used.

So, in order to inhibit the dopping rule with pudDate of feed, protocol has to say explicitly all 9 fields are mandatory.

I do not say if feed from seti@home is right or wrong.
Because I haven't read the protocol, I can't say for sure which.
I expect, following the above rule, seti@home may drop time field in the pubDate, rightmost 5 fields out of 9 fields.

---

In general, with the character string representation of time (9 fields), there is such an understanding that fields can be dropped from right to left. This is a kind of defacto standard, this is always meant implicitly anywhere it is used.

So, in order to inhibit the dopping rule with pudDate of feed, protocol has to say explicitly all 9 fields are mandatory.

I do not say if feed from seti@home is right or wrong.
Because I haven't read the protocol, I can't say for sure which.
I expect, following the above rule, seti@home may drop time field in the pubDate, rightmost 5 fields out of 9 fields.

the rss spec states that full ISO dates must be used, and the feed validator will complain if they're cut short (if they're "short" they're no longer ISO dates

feed validator results for SETI feed

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Engines

>the rss spec states that full ISO dates must be used, and the feed validator will complain if they're cut short (if they're "short" they're no longer ISO dates

I would interpret "full" as admitting full scope of usage including truncating.

In this light, validator is biased to an interpretation; It isn't to give certificate; It is to attract our eyes on points where human verification may better be applied.

---