Replies

• 
  Joe 8 years ago

  I agree @zinnius. I think it just moves the privacy problem around to different systems. If any thing the communication between nodes is another vector for privacy violation. I also don't think it makes you in control of your data as it still gets shipped around the nodes and you didn't sign up for them or have to trust them.

  • 0
• 
  Zinnius 8 years ago

  If you look at #Diaspora or #Friendica, what is the result after all those years? It's sadly just a niche thing.

  • 1
• 
  Joe 8 years ago

  @kwinto it depends. It is relatively easy to do even for web development. We already have a strict build cycle on this site, commit pr -> continuous integration -> merge to master -> deploy. It would make little difference if we got a binary asset at the end or not.

  • 0
• 
  Joe 8 years ago

  XMPP is one of the better ones. But it is outdated in many places.

  • 0
• 
  Joe 8 years ago

  You will eventually end up with email given enough time and we know how good that is for privacy.
  
  I agree with @koe also. It can be a pain when dynamic/system libs are required across distributions.
  
  I know they're quite popular but time is against them I think.
  
  We are still thinking about adding it here but all these questions keep coming up. Pjuu would need re-writting so we get a static binary from the source and would have to be auto updatable on the nodes.

  • 0
• 
  Joe 8 years ago

  This is a tough one and I do have my same reservations about federated systems. I guess it depends on what you want out of it. I think it is very hard to make changes expecting all others in the network to update the software. Also if you follow one of the current fed protocols you are just going to create the same thing. With encryption this is also harder as it requires all nodes to communicate at the same level if there is a bug found in the protocol.

  • 0