Conversation

Notices

1. MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 03-Feb-2016 21:34:42 UTC MMN-o ✅⃠

   • Bastian Ilso
   @bastianilso Ah, subscribers wouldn't be preserved anyway in the backup method we have right now... But we have full #FOAF support! So that's a good place to start if you want to do any "triangulation" :)
   Check out the Linked Open Data cloud for example: http://lod-cloud.net/ (the big section of #StatusNet accounts, that's us).
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 03-Feb-2016 21:25:47 UTC MMN-o ✅⃠

     • Bastian Ilso
     @bastianilso In theory yes, in practice I wouldn't try it (buggy). It'd be nice to make sure it works for future versions but it's not a high priority. (microblogging is sort of a fleeting area of communication anyway)
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 03-Feb-2016 21:42:33 UTC MMN-o ✅⃠

     in reply to

     • gnusocial
     • Bastian Ilso
     @bastianilso Oh, you didn't mean that with "triangulation". Right. To answer that question, !GNUsocial is a _decentralised_ network, not distributed. It's sort of a direct inheritance from the standards we use to distribute data (it's just HTTP-accessible Atom feeds with some extra metadata to describe social activities). I think it's an important feature to remain compatible with your off-the-shelf news feed readers and parsing libraries.
     
     The amount of issues arising with distributed vs. decentralised makes a good case to stick with the current networking model with each server having their own view of the network. A server on the network doesn't know of anything it hasn't been actively told by a third party or asked to look up via interactions of its users.