replies to federated users don't go through if local user with same name exists
replies to federated users don't go through if local user with same name exists
| Issue ID: | 2542 |
| Issue Category: | bug |
| Component: | uncategorized |
| Priority: | major |
| Status: | active |
| Assigned: | Unassigned |
| Version: | 0.9 |
I used to use the account 'mrb' on identi.ca. I now use an account 'mrb' on my own server. With some regularity if users reply to mrb from an identi.ca account the notice does not come back to my account on my own server but is put in the notice list of the account on identi.ca.
I can't put my finger on the exact circumstances, but i think it only occurs when the reply-er uses xmpp.
Here's an example:
The original notice with my reply:
http://identi.ca/conversation/46347329#notice-46705125
(notice that 'mrb' is properly linked to mrb@o.mrblog.nl)
The reply of sud)er is here:
http://identi.ca/conversation/45485887#notice-46705739
attached to a totally unrelated notice of me (but the last of the mrb account on identi.ca)
I would have never seen the reply of sud0er if I had not looked at identi.ca

Updates
#1
Yeah, if they're manually writing '@mrb blah blah' I think it might not pick up correctly who it should be sending to (if the notice is marked as being a reply, as when using 'reply' button on the web or using the reply command in xmpp, then it should always include the right destination).
We might need some additional smarts in the mentions resolution... though also a 'forward replies' option to help with moving accounts could help.
You can also subscribe to the
RSS feed for updates to this issue.