1) I know that Status.Net understand activitystreams object entry. Does it also encompass activity entry?? Of course those entries that incorporate an <activity:verb>, <activity:object> and an <activity:object-type>. (section 5.1 of activitystrea.ms specs)
2) I have a try at a swat0 test using three Status.Net accounts: Alice <------- Bob --------> Andrea 1)Bob takes a photo and tag Alice. 2)Alice receive the mention using Salmon. 3)Andrea who is subscribed to Bob, receive the tagged photo; Afterwards he posts a reply. 4)The reply swims upstream (Bob) using Salmon so it is incorporated in Bob conversation. 5)The reply does not reach Alice!!!!! (SWAT0 fails) I have thought and implemented a light solution for my personal microblog. Why don't create a feed containing all the replies involved in the conversation(Bob post) and make this feed available throughout a <link rel="replies" thr:count="x" thr:updated="last date" href="link-to-the-reply-feed" /> element [from Atom Threading Extensions] contained in the original(BOB) "pubsubhubbub feed" entry?? Whenever BOB receives a reply, he should only update the thr:count and thr:updated in his entry and pubsubhubbub would delivery this update to all his followers(hence ALICE!!). On the client/follower side (ALICE), every time that a duplicated post is received through pubsubhubbub, it would entail the search of the link with rel = replies and the reply-feed retrieval, which would be processed in the right manner looking for new replies. Replies that are not owned by the publisher of the feed (so those from Andrea), are incorporated in the reply-feed using the <me:provenance> [from Salmon spec] element inside the entry (it is the Salmon(reply) received by the owner of the conversation), therefore the "client/follower" can be able to authenticate the notice(reply) contained in the replies-feed. Lets me know if you can implement this kind of solution into Status.Net and make so the conversation more integrate.thanks. -- *Politecnico di Torino* *Andrea Messina*
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
