Salmon The Secret Weapon of the federated social web

Goals

Notes

OStatus's usage of Salmon goes slightly beyond the original intent of blog commenting by sending (potentially open-ended) ActivityStreams entries. This can complicate handling addressing, since a comment with threaded reply-to and an AS 'like' entry etc might need quite different handling. This is probably ok, though, since the endpoint needs to know how to handle the type to make good use of it.

Is the PKI part important, or an extra annoyance that can be discarded? Dial-back for delivery verification is probably sufficient for most purposes, but loses the ability to verify a signature as we send a message over multiple hops.

"Salmon is really 3 specs"

• PKI
• Signed messaging
• Moving messages between services

Outcomes

== People