[ostatus] without 'reply-to' in specification of OMB, some notices appear in the wrong context/conversation

Submitted by Graham Perrin on Mon, 12/28/2009 - 21:13

Issue ID:	2109
Issue Category:	bug
Component:	omb
Priority:	major
Status:	fixed
Assigned:	evan
Version:	0.9
Milestone:	0.9
Keywords:	reply-to ostatus

= Example =
http://brainbird.net/notice/1186374
* true context is http://brainbird.net/conversation/1185234#notice-1186374
* false context is http://identi.ca/conversation/17339719#notice-17362324

Legacy Data

This issue was migrated from another tracking system. The legacy data at time of import is provided below as a reference.

Ticket ID:

2109

Reported by:

grahamperrin

Owner:

evan

Status:

new

Type:

bug

Component:

omb

Priority:

Version:

0.9

Milestone:

0.9

Updates

#1

Submitted by Graham Perrin on Wed, 12/30/2009 - 08:19.

'''More examples''' discussed at http://brainbird.net/conversation/894593#notice-894593

#2

Submitted by Brion Vibber on Wed, 01/13/2010 - 15:58.

Just noting that this needs reply-to information added to the protocol (and not 100% sure how easy that is to do and maintain over multiple sites)

#3

Submitted by Graham Perrin on Thu, 01/14/2010 - 01:40.

Thanks. Also noting and with more formal stuff to follow.

#4

Submitted by Brion Vibber on Mon, 03/01/2010 - 23:41.

Reply & conversation info should now be preserved when posting over ostatus, but haven't confirmed all is working yet.

#5

Submitted by Graham Perrin on Thu, 03/11/2010 - 01:41.

Replying to [comment:5 brion]:
> Reply & conversation info should now be preserved when posting over ostatus, but haven't confirmed all is working yet.

#2231 is ''conversations between Identi.ca and hosted !StatusNet Cloud Service (SCS) are incomplete'', but I'm not sure whether both environments in that ticket satisfy the requirements for conversation.
----
Replying to [ticket:2109 grahamperrin] and focusing on the subject of this ticket:
> '''some notices appear in the wrong context/conversation'''
* on one hand, I haven't seen that symptom in a while
* on the other hand, I haven't used Identi.ca/StatusNet services much in recent months.