IDNet RSS Feed

Rik · Nov 09, 2010, 17:38:18

How about on the validation site, Bill.

Bill · Nov 09, 2010, 17:53:27

Oops, didn't see that

Combined feed:

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
line 47, column 3: description should not contain HTML: h2 (10 occurrences) [help]
]]></description>

Usage feed:

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
line 47, column 3: description should not contain HTML: h2 (5 occurrences) [help]
]]></description>

Status feed:

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 2, column 446: Missing atom:link with rel="self" [help]
... iencing no problems</description></item></channel></rss>

I've red-bolded the character that had a circumflex under it, presumably the start of the problem..

Rik · Nov 09, 2010, 17:56:24

Thanks, Bill. The fact that we get different reports from the same source does increasingly make me think it's something to do with the customer ID in the combined and account feeds. Nothing else should change.

Of course, I'm probably completely wrong.

Bill · Nov 09, 2010, 18:06:09

It's all Greek to me... the only thing I know about RSS is what the letters stand for

Rik · Nov 09, 2010, 18:10:12

I thought that would have been all geek to you, Bill.

What I'm getting as is that if my two account-related URLs are failing, but yours are not, while for both of us the network URL, which is universal, works, it makes me wonder what difference could cause the failure, and the only one I can think of is the 'identifier' section of the URL which deals with the account.

Bill · Nov 11, 2010, 15:01:37

Did this get fixed? Just curious.

A difference I've noticed- the old combined feed used to give me status messages that were nicely formatted, just like on the main status page, on the new feed all the EOLs seem to have been stripped out and I just get a wodge of hard-to-read text.

Anyone else, or just me?

Usage feed is fine.

Rik · Nov 11, 2010, 16:15:42

The format is different, Bill. The problems have been fixed for me. I have two logins for two lines, and although the key generated from my usual one appeared to be correct, it failed to authenticate the other line correctly. Logging into that, and getting the feed there, resolved the problem.

Steve · Nov 11, 2010, 16:23:09

I agree with Bill the RSS IDNet status feed is very difficult to read, the use of the return key (carriage return) in a few places would help greatly.

Rik · Nov 12, 2010, 08:25:48

Martin is working on formatting the RSS feed...

Bill · Nov 12, 2010, 10:38:05

Bill · Nov 19, 2010, 14:16:05

Quote from: Rik on Nov 12, 2010, 08:25:48
Martin is working on formatting the RSS feed...

It didn't work

Ray · Nov 19, 2010, 14:44:33

Something's been fixed I've just started getting the RSS Status feeds through in Outlook again.

Rik · Nov 19, 2010, 15:24:51

I'm just trying to get the two feeds rationalised, there's still more in the full customer feed than in the network status only version.

Glenn · Nov 20, 2010, 12:12:06

At 10;22 I got notification that Livingstone Mux is having problems, yet 2 minutes later another RSS update saying "BT have no current incidents"

Rik · Nov 20, 2010, 12:24:54

I've got two on Livingstone, but nothing else, Glenn.

Ray · Nov 20, 2010, 13:20:39

I've only had the 2 Livingstone ones as well, I did get a 'no BT incidents one' yesterday though.

Bill · Nov 20, 2010, 14:00:41

Ignoring a few "No problems at BT" updates at various times, I've had a Livingston report at 10:21, Livingston and Edinburgh at 10:35, then Edinburgh at 11:57, 12:05 and 12:33.

Ten assorted reports yesterday, including 6 re Herriard

edit- no real information in any of them, just a link (given twice!) to a web page with the details.