Currently I'm refactoring User-related part of #AndStatus data model using recent amendments of #ActivityPub specification, which I initiated: distinction between a User (a real life person or an organisation...), Accounts of this user in concrete instances (Servers) of the global social network, and an Actor - the entity, which is actually present in Activities of the ActivityPub protocol.
Very helpful clarifications, allowing me to express clearly relations between different things inside the application. For example, now I'm working towards creation of views on a User across all networks, logically merging Actors of this User.
As a result, at the first step you will see e.g. actions/messages by andstatus@quitter.no Actor as actions by ONE Actor, even if you see these actions via several Servers, e.g. via mastodon.social and via GnuSocial.no, as on the attached screenshot.
The next step will be to merge Actors of one User into one view. E.g. set andstatus@loadaverage.org and andstatus@mastodon.social Actors as _one_ User. This cannot be done automatically due to current limitation of the #ActivityPub specification, but at least can be done manually for selected Users that you follow via their Actors in different networks... https://loadaverage.org/attachment/4021406