UserPreferences

FeedcastNameDiscuss


Background

[JesseJamesGarrett] We must plan for this name to reach many, many more people than your typical open-source project or XML-based data standard. This project is the vehicle for syndication technology to make the leap to a broad, non-technical, non-power-user audience.

For this reason, the name must be consumer-friendly. We cannot assume that our product is compelling enough to overcome a name that does not resonate with the consumer market.

The name should be semantically related to the ideas inherent in this technology. The name must provide a simple hook for the complex idea of syndication. The name is the consumer's gateway to the set of concepts they must learn in order to appreciate, adopt, and ultimately use the technology.

Attributes

URLs

(Thanks Rick!)

Taglines

Usage

Icons

http://merau.pair.com/~spidery/feedcast/feedcast_enabled.png , http://merau.pair.com/~spidery/feedcast/feedcast_secure.png , http://merau.pair.com/~spidery/feedcast/feedcast_xml.png , http://merau.pair.com/~spidery/feedcast/feedcast_valid.png

Discuss

[TomasJogin] Might seem irrelevant or improper to someone who's (for example) looking for an API to update a CMS over http, but has no intention or thought of making a "feed".

[NickChalko] Feedcast sounds like failed push technology from the 90's.


CategoryNameDiscuss