Expose both `feed.title` and `feed.text` about listparser

[kurtmckee]

I think I understand your use case now, and I appreciate the example case you provided!

However, I don't think listparser should help resolve this issue.

[kurtmckee]

listparser supports 3 different XML formats. While OPML is the most common by far, listparser was written to support OPML, FOAF (used by e.g. the LiveJournal platform, Planet Mozilla, Planet Gnome, etc), and iGoogle (which Google shut down a few years after listparser added support).

listparser's goal is to give feed readers access to basic information about the feed or subscription list:

1. A URL (mandatory)
2. The title of the feed or subscription list that the user set
3. Category or tag information that the user set

listparser doesn't attempt to map OPML XML attributes directly to Python attributes, and its goal is not to expose all XML elements and attributes from the supported XML formats. I don't want listparser to expose multiple attributes by name; I only want it to expose information that feed readers need to import the user's title/catorgery/tag information.

[Rongronggg9]

I only want it to expose information that feed readers need to import the user's title/catorgery/tag information.

I agree with that. But does the current behavior really provide enough "information that feed readers need to import the user's title"? Why is it important to determine if the title is user-defined or not? Can't the feed reader just fetch the feed once, and then compare its title with feed.title from listparser? Let's imagine such a case:

1. Some feeds occasionally update their title ("remote title").
2. An RSS reader may be implemented to follow the remote title change unless users have defined their custom title.
3. A user exports OPML from the RSS reader as a backup. Each feed's outline comes with text attr (user-defined title, if available, else feed title) and title attr (always feed title).
4. Days later, some of these feeds happen to update their titles.
5. The user imports the OPML into the RSS reader on a new device.
6. If we can only compare feed.title from listparser with the fetched title ("remote title"), since they differ, feed.title from listparser can only be considered as user-defined. As a result, it will override the remote title. The user may consider this an undesired behavior if they want the title in the RSS reader to follow the remote one every day.
7. My proposal is a solution to the above case.

I admit that the case may be an edge case. If you consider it "out of listparser's business", nevermind :)