<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://cyborganthropology.com/index.php?action=history&amp;feed=atom&amp;title=Salmon_Protocol</id>
	<title>Salmon Protocol - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://cyborganthropology.com/index.php?action=history&amp;feed=atom&amp;title=Salmon_Protocol"/>
	<link rel="alternate" type="text/html" href="https://cyborganthropology.com/index.php?title=Salmon_Protocol&amp;action=history"/>
	<updated>2026-05-07T22:39:18Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://cyborganthropology.com/index.php?title=Salmon_Protocol&amp;diff=485&amp;oldid=prev</id>
		<title>Caseorganic: Created page with &#039;Does Salmon support threading?  Yes, the thr:in-reply-to ID can be the ID of a comment (which can itself be a Salmon with a xpost:source element that points at the ultimate sourc…&#039;</title>
		<link rel="alternate" type="text/html" href="https://cyborganthropology.com/index.php?title=Salmon_Protocol&amp;diff=485&amp;oldid=prev"/>
		<updated>2010-05-14T18:07:54Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;#039;Does Salmon support threading?  Yes, the thr:in-reply-to ID can be the ID of a comment (which can itself be a Salmon with a xpost:source element that points at the ultimate sourc…&amp;#039;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Does Salmon support threading?&lt;br /&gt;
&lt;br /&gt;
Yes, the thr:in-reply-to ID can be the ID of a comment (which can itself be a Salmon with a xpost:source element that points at the ultimate source).  While the protocol supports threading, recipients can of course flatten salmon in the feeds that they re-publish -- though the thr:in-reply-to element can be used to reconstitute threads as needed. &lt;br /&gt;
&lt;br /&gt;
How is Salmon different from using AtomPub to post to a comment feed?&lt;br /&gt;
Salmon is in fact based on and compatible with AtomPub. Salmon greatly enhances interoperability and usability by specifying a distributed identity mechanism for identifying the author and intermediary involved, provides a discovery mechanism, and specifies how things should be linked together.  By not requiring pre-registration or federation but still allowing for verifiable identification, it provides a usable, level playing field for all parties involved.&lt;br /&gt;
Why are you using this new crosspost extension instead of just using, and retaining, atom:id?&lt;br /&gt;
&lt;br /&gt;
See http://wiki.activitystrea.ms/Cross-Posting.&lt;/div&gt;</summary>
		<author><name>Caseorganic</name></author>
	</entry>
</feed>