dir/view/fake_feed.tpl

<?xml version="1.0" encoding="utf-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom" >

  <id>fake feed</id>
  <title>fake title</title>

  <updated>1970-01-01T00:00:00Z</updated>

  <author>
    <name>Fake Name</name>
    <uri>http://example.com</uri>
  </author>
magic-envelope verification, status.net appears to do it wrong. Ultimately we need to do it right (or why bother having a spec?), and fallback to doing it wrong if we're talking to a broken system - which ironically seems to include most of the federated social web projects. 2010-10-21 13:53:43 +02:00			`<?xml version="1.0" encoding="utf-8" ?>`
rely on feed item (e.g. salmon) to declare namespaces. This way we don't cause conflict with any chosen NS prefix in the feed 2010-10-22 05:51:21 +02:00			`<feed xmlns="http://www.w3.org/2005/Atom" >`
magic-envelope verification, status.net appears to do it wrong. Ultimately we need to do it right (or why bother having a spec?), and fallback to doing it wrong if we're talking to a broken system - which ironically seems to include most of the federated social web projects. 2010-10-21 13:53:43 +02:00
			`<id>fake feed</id>`
			`<title>fake title</title>`

			`<updated>1970-01-01T00:00:00Z</updated>`

			`<author>`
			`<name>Fake Name</name>`
			`<uri>http://example.com</uri>`
			`</author>`
rely on feed item (e.g. salmon) to declare namespaces. This way we don't cause conflict with any chosen NS prefix in the feed 2010-10-22 05:51:21 +02:00