I'm going to list some (major and minor) issues raised during Ostatus testing of Status.Net account:
1) Salmon signature does not complain with the spec [Magic Signature]: http://salmon-protocol.googlecode.com/svn/trunk/draft-panzer-magicsig-00.html <http://salmon-protocol.googlecode.com/svn/trunk/draft-panzer-magicsig-00.html>2) Status.Net replies are all MENTIONS. Afterwards, all the mentions are incorporated in the profile feed and sent throw Pubsubhubbub and Salmon!! (bandwidth overhead!!!!) I have noticed that if i send a Post using pubsubhubub and then i send the corresponding reply, still using pubsubhubbub and not Salmon; Status.Net does not incoporate the two messages in the same conversation. 3) Status.Net conversation aren't fragmented ONLY in the SOURCE. I think it would be nice to have the same conversation replicated to all the Followers....For instance, we could reach this behaviour, incorporating the replies post(local and remote) in the source atom feed and delivering them using pubsubhubbub. Cheers -- *Politecnico di Torino* *Andrea Messina*
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
