Dig A Hole
External Feeds
Posts Calendar
May 2012 |
||||||
|---|---|---|---|---|---|---|
| S | M | T | W | T | F | S |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Content is king Long live content !!
Distributing content via RSS is not new. However displaying the content within your own site is !!.
Let me try to explain we would never advocate plagiarism but the content within the RSS feed is in the public domain.
The usual feed contains a most of the content of the web site it originated on. However most aggregators (feed displayers) show minimized content (description and a link back) forcing you to visit the originators site to view the full article.
We have just completed an object that effectively pulls and displays the full content of the feed within your own site.
Here is an example of F1 Jake Humphry's blog distributed by the BBC Formula One Site Here .
In this instance the content is pulled from the BBC site and displayed from within our site structure. All the content is beond your control as its generated by the content provider in this instance the BBC.
Why is this functionality important to us ? Lets say I'm a night club owner with live music three times a week managing my website content to reflect my performers can become a nightmare task for my site administers cutting and pasting content from one site to another. Not any more you can effectively just request a RSS feed from the bands and display their content from within your own site.
To take this a stage further we have the ability for users to save the content into a database and manipulate the content as if you owned it (well effectively you do). The problem we have a present the inconsistency of the feed structure so not an automated process at present.
Perma Link
Randomised YT F1 2100
Tenby Weather

- Temp: 48°F
- Clouds: mostly cloudy
