andstatus
andstatus copied to clipboard
Treat different "GNU social" systems as one "GNU social" federation
Currently AndStatus treats different microblogging systems of StatusNet type as totally unrelated. This causes a lot of duplicated dents (messages) and users, each of which belonging to different system but being actually the same dent/user, transferred between these systems inside common network ("GNU social" federation) and getting local ID in each of the system.
However, there is a way to easily find duplicate dents: they have the same globally unique identifier in the "uri" field of JSON object (for a user: "statusnet_profile_url")
The questions are: Q1. Which of duplicated dents should be kept? Which of duplicated Users should be kept? Q2. How do we link together dents from different systems, if they are really parts of the same conversation?
Possible solution:
- We create another, virtual Microblogging system, called "GNUsocial", meaning the global "federation". In "GNUsocial" both messages and users have GUIDs, described above.
- We store common part of dents and users as belonging to the "GNUsocial" + create additional tables to store "local ids" of dents and users in all systems - members of the federation, from which we are receiving the same dent/user.
- Inside AndStatus we use AndStatus local IDs, but when deciding about linking of newly received dent/user we resolve AndStatus local IDs via "local ids" of the source system and GUIDs.
I think you can close this issue, all the StatusNet servers are evolving to GNU social (or at least, it's how I see it)
@moshpirit In order not to confuse readers, I renamed the issue. Actually, the task is very important, because currently, having accounts in several GNU Social instances, I have a lot of duplicated users and messages...
Ok! no problem :)
See this related conversation https://loadaverage.org/conversation/6719494#notice-6721302
This is another conversation discussing addition of Pump.io API to GNU Social sites. This will allow AndStatus to achieve even more than this issue suggests: GNU social plus Pump.io will be one federation from AndStatus's point of view. AndStatus is ready for this change as it supports Pump.io API. See https://social.umeahackerspace.se/notice/127279