28 February 2005

How I broke NewsGator's Platform: Sorry!

While doing some experiments with tags, I broke the NewsGator Template.

First, the good news: I know what happens if you type more than 52,755 characters: NewsGator can't handle it.

Now the bad news: If you type more than 52,755 characters, guess what happens? The content at the end gets cut off; if you have HTML at the end, the feed-content may bleed into the next.

Imagine what happens if you have multiple-reports of the same feed that bleeds into each other. It is a mess.

If you want to see the result; after you put that URI into NewsGator you may have a problem viewing it. Here's the original blog for comparison

It looks like what happens is that if you type more than the maximum number of characters, the end of the post gets cut off. Then, if you have HTML at the end of the feed, the part that doesn't show up...can affect the next display.

In my case, the only way I could have published the content was if the HTML was valid; blogger doesn't allow HTML to get published unless its well formed. The override option no longer works.

Suggestions

If the number of characters in the particular published item exceed the maximum allowable, then strip out the HTML and only show content. This will let those feeds that have full content still post.

Another option is to post only a summary of the long blog-to-feed entry. Post a message in the feed-result to the reader that the posted element is only a summary, and has been truncated because of HTML formatting.

Another more complicated approach would be to read through the reported feed [that shows up], then close out all the HTML in order to create a single-valid output. All the content that is above the "natural ending items" would then get cut off.
While doing some experiments with tags, I broke the NewsGator Template.

First, the good news: I know what happens if you type more than 52,755 characters: NewsGator can't handle it.

Now the bad news: If you type more than 52,755 characters, guess what happens? The content at the end gets cut off; if you have HTML at the end, the feed-content may bleed into the next.

Imagine what happens if you have multiple-reports of the same feed that bleeds into each other. It is a mess.

If you want to see the result; after you put that URI into NewsGator you may have a problem viewing it. Here's the original blog for comparison

It looks like what happens is that if you type more than the maximum number of characters, the end of the post gets cut off. Then, if you have HTML at the end of the feed, the part that doesn't show up...can affect the next display.

In my case, the only way I could have published the content was if the HTML was valid; blogger doesn't allow HTML to get published unless its well formed. The override option no longer works.

Suggestions

If the number of characters in the particular published item exceed the maximum allowable, then strip out the HTML and only show content. This will let those feeds that have full content still post.

Another option is to post only a summary of the long blog-to-feed entry. Post a message in the feed-result to the reader that the posted element is only a summary, and has been truncated because of HTML formatting.

Another more complicated approach would be to read through the reported feed [that shows up], then close out all the HTML in order to create a single-valid output. All the content that is above the "natural ending items" would then get cut off.
" />