New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Salmon for WordPress | You have to log in to add a translation. | Details |
Original untranslatedMeta |
|||
| ↑ | Salmon | You have to log in to add a translation. | Details |
Original untranslatedMeta |
|||
| The payload can define any kind of message, so Salmon can be extended in arbitrary ways. It is already being used to communicate mentions to mentionees. It has also been used to signal cross-site following (by sending a follow message) or to send requests (by sending requests rather than notifications, e.g., a friend request). It is best used when there is not necessarily predefined relationship or subscription between the source and destination; if there is, PubSubHubbub may be a better choice. | You have to log in to add a translation. | Details | |
Original untranslated
The payload can define any kind of message, so Salmon can be extended in arbitrary ways. It is already being used to communicate mentions to mentionees. It has also been used to signal cross-site following (by sending a follow message) or to send requests (by sending requests rather than notifications, e.g., a friend request). It is best used when there is not necessarily predefined relationship or subscription between the source and destination; if there is, PubSubHubbub may be a better choice.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| See <a href="http://wiki.activitystrea.ms/Cross-Posting">http://wiki.activitystrea.ms/Cross-Posting</a>. | You have to log in to add a translation. | Details | |
Original untranslated
See <a href="http://wiki.activitystrea.ms/Cross-Posting">http://wiki.activitystrea.ms/Cross-Posting</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| All of this is possible to do, and has been done, with closed systems. Salmon provides a way to do this with an open protocol that anyone can implement and anyone can interoperate with. | You have to log in to add a translation. | Details | |
Original untranslated
All of this is possible to do, and has been done, with closed systems. Salmon provides a way to do this with an open protocol that anyone can implement and anyone can interoperate with.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Assuming wide deployment, we expect that spammers will attack Salmon with the same vigor they throw at email. However, Salmon implementors can cheaply and easily deal with the simpler techniques the spammers currently use to inject email. They will also mount active defenses based both on the years of experience in spam-blocking email and the new tools (guaranteed identity, identity providers, distributed reputation) that Salmon enables. | You have to log in to add a translation. | Details | |
Original untranslated
Assuming wide deployment, we expect that spammers will attack Salmon with the same vigor they throw at email. However, Salmon implementors can cheaply and easily deal with the simpler techniques the spammers currently use to inject email. They will also mount active defenses based both on the years of experience in spam-blocking email and the new tools (guaranteed identity, identity providers, distributed reputation) that Salmon enables.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Salmon disallows completely anonymous and untraceable messages. It requires pseudonyms from verifiable identity providers. This feature allows receivers to rate limit the messages per hour per pseudonym and per identity provider. (Identity providers themselves have verifiable identities and can gain or lose reputation based on what their users do; every identity provider has to at least have a domain name, raising the bar for spammers significantly, and meaning that simple rate limiting can force the spammers to acquire and "burn" many domain names.) | You have to log in to add a translation. | Details | |
Original untranslated
Salmon disallows completely anonymous and untraceable messages. It requires pseudonyms from verifiable identity providers. This feature allows receivers to rate limit the messages per hour per pseudonym and per identity provider. (Identity providers themselves have verifiable identities and can gain or lose reputation based on what their users do; every identity provider has to at least have a domain name, raising the bar for spammers significantly, and meaning that simple rate limiting can force the spammers to acquire and "burn" many domain names.)
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Specifically, spammers can not forge signatures from legitimate users, and it is very hard for them to mint massive numbers of fake identities without detection. So as a first line of defense, anything whose authorship check fails, is simply dropped. We're building this in from the start so that we'll never have an installed base of clients doing things insecurely. | You have to log in to add a translation. | Details | |
Original untranslated
Specifically, spammers can not forge signatures from legitimate users, and it is very hard for them to mint massive numbers of fake identities without detection. So as a first line of defense, anything whose authorship check fails, is simply dropped. We're building this in from the start so that we'll never have an installed base of clients doing things insecurely.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Salmon tries to find a good balance. Salmon adopts a defense-in-depth strategy, assumes that there will be abuse and spammers, but builds in protocol hooks to make an active in-depth defense both cheap and effective with few false positives. | You have to log in to add a translation. | Details | |
Original untranslated
Salmon tries to find a good balance. Salmon adopts a defense-in-depth strategy, assumes that there will be abuse and spammers, but builds in protocol hooks to make an active in-depth defense both cheap and effective with few false positives.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| Early Internet protocols and systems were vulnerable to trivial forgery, and fixing this after the protocols were widely deployed is painful, partial, and slow. On the other hand, it's also possible to add too much security and make a protocol too restrictive or too complex for large-scale adoption. | You have to log in to add a translation. | Details | |
Original untranslated
Early Internet protocols and systems were vulnerable to trivial forgery, and fixing this after the protocols were widely deployed is painful, partial, and slow. On the other hand, it's also possible to add too much security and make a protocol too restrictive or too complex for large-scale adoption.
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| The FAQ is taken from the Salom Protocol homepage: <a href="http://www.salmon-protocol.org/faq">http://www.salmon-protocol.org/faq</a> | You have to log in to add a translation. | Details | |
Original untranslated
The FAQ is taken from the Salom Protocol homepage: <a href="http://www.salmon-protocol.org/faq">http://www.salmon-protocol.org/faq</a>
CommentFound in faq paragraph. You have to log in to edit this translation. Meta |
|||
| What else is Salmon useful for? | You have to log in to add a translation. | Details | |
Original untranslated
What else is Salmon useful for?
CommentFound in faq header. You have to log in to edit this translation. Meta |
|||
| Why are you using this new crosspost extension instead of just using, and retaining, atom:id? | You have to log in to add a translation. | Details | |
Original untranslated
Why are you using this new crosspost extension instead of just using, and retaining, atom:id?
CommentFound in faq header. You have to log in to edit this translation. Meta |
|||
Export as
Comment
Short description.