- 1 IndieWeb Examples
- 2 Projects
- 3 Autodiscovery
- 4 Comments
- 5 Shutdowns
- 6 Criticism
- 7 History
- 8 See Also
Tantek Çelik generates (using Falcon) a minimal subset Atom+ActivityStreams feed on tantek.com from storage. Due to bandwidth inefficiency of XML formats (and apparent bandwidth abuse of XML consuming code/servers), his Atom feed file only has the most recent 1 item(s), whereas his h-feed on his home page has the latest 64 items (as of 2015-265). See also feed file: Criticism and in particular feed: Criticism.
- The feeds are automatically generated from the h-entry microformats on the page, so I only have to maintain the HTML which works for humans and machines rather than two copies. The endpoint I use for converting is open for anyone to use: microformats to ATOM --Barnaby Walters 10:17, 10 February 2015 (PST)
Christian Weiske's blog natively generates full-text atom feeds for tag-filtered and all posts
Kyle Mahan publishes an Atom feed for all post feeds (most recent iteration since 2014-09-13).
- add ?feed=atom to any regular feed for an Atom version. e.g.,
- Entries includes simple reply/repost context
gRegor Morrill publishes an Atom feed for articles as of 2015-02-11
- Previously I was publishing an RSS 2.0 feed that was delivered by FeedBurner. I migrated back to a self-hosted feed due to the unsure future of FeedBurner, plus having more control of the feed since it is on my own domain again.
- Have XSL for viewing from a browser (blog post)
- Feed is limited to 30 posts with only the first 10 full text
hfeed2atom converts h-feeds to atom feeds.
- unmung generates an h-feed from any Atom or RSS one
Atom feeds can be automatically discovered by feed readers if the homepage contains a link to it in its <head> tag:
<link rel="alternate" type="application/atom+xml" title="Feed" href="atomfeed.xml" />
The title is important if there are multiple feeds linked, e.g. category and comment feeds.
The Atom Threading Extensions RFC 4685 extends the Atom XML format to allow direct embedding of comments for posts/entries in the atom feed, as well as linking to comment feed files for single posts.
Software generating Atom feeds with comments:
readers supporting atom comments:
- https://david.shanske.com/feed/atom/ contains:
<entry> [...] <link rel="replies" type="text/html" href="https://david.shanske.com/2018/03/18/an-indieweb-podcast-episode-0/#comments" thr:count="11"/> <link rel="replies" type="application/atom+xml" href="https://david.shanske.com/2018/03/18/an-indieweb-podcast-episode-0/feed/atom/" thr:count="11"/> <thr:total>11</thr:total> </entry>
See: Feeds: Shutdowns
This section is a stub. For additional history see Wikipedia: Atom Development History (though it may not have all the details present here).
- 2003-06-16 The effort to define a "conceptual data model of what constitutes a well formed log entry" blogged by Sam Ruby in Anatomy of a Well Formed Log Entry was the start of what became Atom.
- 2003-06-23 the effort that became Atom was more formerly launched, with various supporting blog posts in the following days. A small sample from the launch roadmap:
Pie was the original name given the to the syndication format project that became Atom. Early posts/pages that mention Pie and its use as a starting point
Echo was the second name given the to syndication format project that became Atom. Early pages/posts that mention Echo:
- 2003-06-29 Ben Trott: Why We Need Echo (original permalink dead: www.sixapart.com/blog/2003/06/why-we-need-ech.html )
- Pie wiki: Echo Conflicts With Another Project
RSS Atom wars
See: RSS Atom wars for citations and quotes from articles during this time period that illustrate the tensions and conflicts.