@verius I would say that this is a deficiency of GNU Social and its "Twitter compatible API". Every instance can have its own user with the same username. This is why it is impossible to tell reliably to which domain "@username" refers. AndStatus assumes that if you refer to a person via @username then this user belongs to your domain...
Interested in exact logic, want to help? @maiyannah
@verius In order to have a reliable system, we need a decision of GNU Social developers. Trying to hack each other is a waste of time... @maiyannah @lnxw48
Looking at the atom protocol and the existing PumpIO class in AndStatus it may be interesting to look at the native atom protocol. I'll do some experimentation over the weekend. If nothing else it'll be a good refresher for my Java skills. :)
@verius Thank you, will try to use Atompub documentation but applying .json extension. And let you know. Regarding reference implementation I understand that this will be the first implementation :-) @mmn
@verius Thank you for investigation, could you for transparency and deeper analysis post the json file (in Activity Streams format) under discussion to this new ticket: https://github.com/andstatus/andstatus/issues/359 "Use Activity Streams API for GNU Social" - I created it for us in order to have a common place for discussion and stop going in circles with the same questions...