Re: More details on using Salmon in OStatus.

7 views
Skip to first unread message
Message has been deleted
Message has been deleted

Markus Sabadello

unread,
Dec 12, 2010, 7:24:21 AM12/12/10
to ostatus...@googlegroups.com
Andrea,

When you post a reply via Salmon, then that reply gets incorporated into the ORIGINAL feed, not into the personal feed of the person writing the reply.

This means that in your Case 1 C does NOT receive B's reply, because B's reply becomes part of A's feed, not part of B's feed.

Markus
--
blog: http://danubechannel.com
phone: +43 664 3154848

On Wed, Dec 8, 2010 at 9:26 PM, Andrea Messina <messin...@gmail.com> wrote:
Hi.
I have a little doubt dealing with the use of Salmon protocol in the
OStatus suite.

My doubts arise from two kind of relationships that we can strike up.

Case 1) Asymmetric friendship:

User A is followed by User B that in turn is followed by User C.

A- - - - - - - - (Punsubhubbub) - - - -  - -> B - - - - - - - - -
(Pubsubhubbub)- - - - - - - - - - - ->C

(When User A makes a new post, this will be notified(PUSH) to User B.
Then when User B makes a new post, it will be notified(PUSH) to User
C).

Now...if User B makes a reply to the post received from User A, it
will be notified(PUSH) to user C(because he follows anything written
by B) which will not understand the <thr:in-reply-to ...> element, and
in the same time, it will be notified to the source(User A) using
Salmon. The comment received from UserA will not update his Profile
Atom(because it is not written by A) and therefore it will not be
pushed to others!!!! (Is it right???)
Now if user A decides to post a further comment on his first post, it
will be only pushed to B....

Case 1 question!!! Why should USERC receive an update written from B
(this is a reply to User A post...) and not the succeeding reply from
A??
Wouldn't be better for USERC to not receive User B reply to userA??

A:
B:                                                  C:
post1 from A                             post1 from
A                                reply from B
 -reply from B                             -reply from B
 -reply from A                             -reply from A


Case2) Symmetric friendship:

User A and B follow each other.

A<- - - - - - - - - -(pubsubhubbub) - - - - - - - ->B

Let's consider the following use case:

UserA makes a post; this post well be received by UserB using
Pubsubhubbub.
Now UserB replies to it.......Is this reply sent to UserA using Salmon
or Pubsubhubbub?????? I think it will be sufficient using
Pubsubhubbub!!!!


thanks...



Andrea Messina

unread,
Dec 12, 2010, 11:11:49 AM12/12/10
to ostatus
Thanks, Markus.

I need some others clarifications.

In the previous message, you say that the reply gets incorporated into
the orginal feed, but i made some tests in vain.
I made a test using a status.net account linked to two friendika
accounts.
All the replies from friendika accounts to a message from Status.Net
one, aren't incorporated neither in the PROFILE/FRIENDS Friendika atom
feed (it's OK), nor in the PROFILE/FRIENDS feed of the
source(status.net), neverthless the overall conversation/context is
properly published in the source (status.net).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-- - - - -- - - - -- - - - - - -- - -

What about mentions??? Surely they are incorporated in the publisher
PERSONAL atom feed....but how are they delivered??
Since they are present in the Atom feed, surely via Pubsubhubbub....so
what is the functionality of the salmon mention endpoint?? When should
i use it to deliver update????

thanks a lot.




On Dec 12, 1:24 pm, Markus Sabadello <markus.sabade...@gmail.com>
wrote:
> Andrea,
>
> When you post a reply via Salmon, then that reply gets incorporated into the
> ORIGINAL feed, not into the personal feed of the person writing the reply.
>
> This means that in your Case 1 C does NOT receive B's reply, because B's
> reply becomes part of A's feed, not part of B's feed.
>
> Markus
> --
> blog:http://danubechannel.com
> phone: +43 664 3154848
>
Reply all
Reply to author
Forward
0 new messages