3 ms·

Simon (https://demo.buddycloud.org/simon@buddycloud.org https://demo.buddycloud.org/simon@buddycloud.org) from the buddycloud team here. Happy to answer any que

Simon (https://demo.buddycloud.org/simon@buddycloud.org https://demo.buddycloud.org/simon@buddycloud.org) from the buddycloud team here. Happy to answer any questions about the bc architecture or our approach.

daenney 14y ago
Obvious question maybe but how does BuddyCloud compare to (and perhaps integrate with) Diaspora?
- Narretz 14y ago
  I remember another effort in distributed social networking, from some months ago. Forgot the name though.
  - premasagar 14y ago
    http://tent.io http://tent.io ?
- imaginator 14y ago
  There's two three things that count when building a distributed social network: easy to use client APIs, Server APIs (how do servers find and connect, catch up, etc) and a reference implementation. I'm not sure that Diaspora has a defined server-to-server API or a client API (can someone more aware of their progress comment). On buddycloud Each domain runs an HTTP API server (https://buddycloud.org/wiki/Buddycloud_HTTP_API https://buddycloud.org/wiki/Buddycloud_HTTP_API) that clients can connect to on their home domain (eg if you are james@giantpeach.com, you connect to something like http-api.giantpeach.com). And servers use XMPP to exchange between one another. Then there is Tentd. I like what they are doing. I think their approach is that every user is a server (your id is http://me.domain.com http://me.domain.com). I'm not quit sure how they federate or resync messages when nodes go down. Can anyone comment on how they federate?
- deleted 14y ago
  [deleted]
karinqe 14y ago
How would my data (say status updates) be stored? On a single server of my own choice? How do you decide who has access to what? Will it be somehow encrypted, so that only a subset of my contact list could get access to a part of it? Would I be able to move all my data to a different server if I decided it is no longer trustworthy?
- imaginator 14y ago
  The unit of sharing is the channel. You start with a personal channel user@domain.com and can create any number of new channels (holiday-photos@domain.com). Each channel has followers, moderator etc that you can control access to (or just set it as public): https://buddycloud.org/wiki/Channels_Explained https://buddycloud.org/wiki/Channels_Explained Think of the architecture like your email provider: You can always grab your mail spool and find a new provider. buddycloud is not dissimilar - just grab your posts and followers from the API and import them on a new provider. We're make this easier soon but, the data and endpoints are all there to facilitate it.
billyjobob 14y ago
Your profile page behaves weirdly when viewed on iPad. The scrolling is jerky and clicking the title bar doesn't scroll to the top like it should.
- imaginator 14y ago
  We know there are problems on the 1st gen iPad. Is that what you are using?
  - billyjobob 14y ago
    no, 3rd

daenney 14y ago

Obvious question maybe but how does BuddyCloud compare to (and perhaps integrate with) Diaspora?

Narretz 14y ago
I remember another effort in distributed social networking, from some months ago. Forgot the name though.
- premasagar 14y ago
  http://tent.io http://tent.io ?
imaginator 14y ago
There's two three things that count when building a distributed social network: easy to use client APIs, Server APIs (how do servers find and connect, catch up, etc) and a reference implementation. I'm not sure that Diaspora has a defined server-to-server API or a client API (can someone more aware of their progress comment). On buddycloud Each domain runs an HTTP API server (https://buddycloud.org/wiki/Buddycloud_HTTP_API https://buddycloud.org/wiki/Buddycloud_HTTP_API) that clients can connect to on their home domain (eg if you are james@giantpeach.com, you connect to something like http-api.giantpeach.com). And servers use XMPP to exchange between one another. Then there is Tentd. I like what they are doing. I think their approach is that every user is a server (your id is http://me.domain.com http://me.domain.com). I'm not quit sure how they federate or resync messages when nodes go down. Can anyone comment on how they federate?
deleted 14y ago
[deleted]

karinqe 14y ago

How would my data (say status updates) be stored? On a single server of my own choice? How do you decide who has access to what? Will it be somehow encrypted, so that only a subset of my contact list could get access to a part of it? Would I be able to move all my data to a different server if I decided it is no longer trustworthy?

imaginator 14y ago
The unit of sharing is the channel. You start with a personal channel user@domain.com and can create any number of new channels (holiday-photos@domain.com). Each channel has followers, moderator etc that you can control access to (or just set it as public): https://buddycloud.org/wiki/Channels_Explained https://buddycloud.org/wiki/Channels_Explained Think of the architecture like your email provider: You can always grab your mail spool and find a new provider. buddycloud is not dissimilar - just grab your posts and followers from the API and import them on a new provider. We're make this easier soon but, the data and endpoints are all there to facilitate it.

billyjobob 14y ago

Your profile page behaves weirdly when viewed on iPad. The scrolling is jerky and clicking the title bar doesn't scroll to the top like it should.

imaginator 14y ago
We know there are problems on the 1st gen iPad. Is that what you are using?
- billyjobob 14y ago
  no, 3rd