Deep thoughts on RSS reading

Deep thoughts on RSS reading

1. Why does an RSS reader encounter a reading bottleneck?

An RSS reader, as a personal reading space, often updates the RSS list slowly after users subscribe to a certain amount of RSS, that is, they seldom Add New RSS, some old RSS feeds are too lazy to be deleted. There are many reasons for this phenomenon. We will analyze them one by one.

(1) reading time bottleneck
The number of RSS subscribed by a user is basically proportional to the user's reading time, while the reading time in a day is limited, which varies from person to person. People who have read more often can subscribe to hundreds to thousands. After the number of RSS feeds approaching the reading time, RSS subscriptions will remain in a slow state for a long time.

(2) reading space bottleneck
The reading space refers to the space part of the RSS interface. For "tree-list-read area" type readers, you can subscribe to a large number of RSS feeds. However, for readers displayed in blocks on Web Desktop, the read space is limited by the display space, when the RSS subscription exceeds the visual endurance, the interest in subscribing to New RSS will also be affected.

(3) reduced reading interest
It is a common process from using RSS reader to generating a certain degree of interest, to enthusiastic searching for RSS, to accumulating the number of RSS subscriptions to a certain extent.

When RSS is subscribed to for a slow period, the source of the new information received by the user is the content of the subscribed RSS, and the source of the user's knowledge is limited. Even more worrying, the content of RSS is only a small part of the website information. After users get used to RSS reading, they seldom get new information from the website that provides RSS.

The problem of solving the RSS subscription bottleneck has been pushed to the RSS reader provider.

2. Is your RSS reader dynamic?

The dynamic here refers to whether the RSS reader can automatically subscribe to the New RSS and automatically clean up the old RSS. As far as I know, there is no such RSS reader. The following are possible solutions.

Solution 1: Subscribe to OPML
Since RSS is changeable, we cannot use RSS as the basic unit of RSS reader subscription. Instead, we should subscribe at a higher level, such as OPML. OPML is the minimum unit of subscription, while the RSS entries in OPML are variable. This is equivalent to choosing a large category to subscribe. For example, IT class. OPML can be provided by independent service providers.

Solution 2: display the split RSS
If RSS is the most basic subscription unit, you have to change the display mode of the RSS reader to achieve the goal of dynamic reading. This is the problem of RSS splitting. Please refer to the following section.

Solution 3: personalized subscription
In this solution, the RSS reader must support the automatic mining of webpage RSS and Intelligent Recommendation functions. Web RSS mining is relatively simple. The intelligence of intelligent recommendations is directly related to the success or failure of this solution. Intelligent recommendations require users to set their own personalized information. After the RSS is mined, the RSS reader obtains the RSS content or even the content of the RSS entries for intelligent matching with the user's personalized information, if appropriate, it is automatically recommended to the user in the corresponding subscription category.

Solution 4: Automatic personalized RSS search
This requires the RSS search engine to support personalized search. Automatic Search and Automatic Recommendation are the key to this solution.

Solution 5: Associate the RSS Service
After a user subscribes to an RSS feed, the user is recommended to the RSS associated with this RSS feed (it is best to support local intelligent recommendations ). When users browse RSS, they also dynamically recommend associated RSS. Associated RSS can be used as an independent service. This type of server can be very detailed and accurate, because this type of service can be implemented in the background by powerful databases and processing capabilities. Before the RSS search service is complete, the associated RSS service will be the most practical service of the RSS subscription service.

3. Why do I need to split RSS?

RSS is a basic unit of reading, which leads to misunderstandings. Now we need to reflect on it.

Taking a blog as an example, articles written by a person are good or bad, and there are various types. They are mixed in the same RSS, which wastes users' reading time and even affects users' reading interests. The real purpose of RSS reader is the product of reading efficiency, so it is necessary to split RSS. RSS reader is Item Based instead of RSS Based.

The split RSS feed will exist in an independent article. This requires a classification system and an evaluation system to allow users to read it quickly and effectively.

We have sniffed the prototype of this split from feedburner, Digg, and Google feed APIs.

Feedburner, by splitting RSS, can get users' comments on each article to provide an article-based ranking system. This improvement will have an important impact on the burner form and bring other related services to the company.

Digg is a system based on user reviews. Its basic unit is an article. If Digg provides RSS subscriptions, the RSS reader can subscribe to high-quality RSS feeds. Of course, this is not the final form of getting RSS, because its RSS, except for a rank value, is no different from ordinary RSS. The improved Digg system will be the best source of RSS subscription.

Google feed API, Google will open its feed user interface, users can use this interface to evaluate any RSS entry, and can also attach their own tags. When this API became a popular review entry for RSS readers, Google had a powerful rank-based RSS/RSS item database. Google once again moved other companies to work.

[Okrss Original article 〕
Http://web2.0focus.com /? P = 31