Will I be able to comment on public posts I receive when I'm following someone?
Will there be a list of people following me? Will it be public? If so it should be possible to turn it off.
What happens to currently broken connections, i. e. when someone has a pending request but the remote pod never received the request?
What happens when the connection can't be established, will the user be notified or just think he is following the remote by never receive anything?
Will there be a flag indicating if its a bi-directional or a follow contact? Will that flag be switched back if one party removes the connection?
Will a contact I'm following be removed from the lists for mentions and conversations so a user isn't trapped on thinking he can and successfully did contact him?
Thanks,
Jonne
Which branch will you be merging? Is that the "follow" branch available through the github repository? It would be good to look at the codeOn Fri, May 13, 2011 at 1:00 AM, Jonne Hass <list-...@mrzyx.home.kg> wrote:
Okay a few questions:
Will I be able to comment on public posts I receive when I'm following someone?
Will there be a list of people following me? Will it be public? If so it should be possible to turn it off.
What happens to currently broken connections, i. e. when someone has a pending request but the remote pod never received the request?
What happens when the connection can't be established, will the user be notified or just think he is following the remote by never receive anything?
Will there be a flag indicating if its a bi-directional or a follow contact? Will that flag be switched back if one party removes the connection?
Will a contact I'm following be removed from the lists for mentions and conversations so a user isn't trapped on thinking he can and successfully did contact him?
Thanks,
Jonne
the longer we drag the big launchthe more time the facecrook guys will have to hatch features that they entrench their users with
(@#uckerburg didn't invest in Diaspora to egg us on)
i still think that it will require
- various ports, some minimal (communicating only the least api to not break the network)
- various hosting providers, oversight by diaspora community, to destroy the bar of entry of running server
Hello Diaspora,
------- TL;DR
We are implementing a new way to connect to people online. �It is getting rolled out next week. It is somewhere in between a follow and a bi-directional relationship. �When you share an aspect with someone, you start seeing their public posts right away. �If they share back, you have a fully bidirectional relationship.
--------
In a few days, we�ll be upgrading Diaspora�s relationship model to something we call the �share� �model. We believe it�s a more elegant way to connect with other people on the network. �We�ve been working on it over the past month, and we�re happy to announce that it�s ready to go. �Before merging this work into Diaspora�s master branch and deploying this feature onto our on servers, we want to give you a heads up and explain what this new model means to both end-users and developers.
At it�s core, �sharing� is how we�re implementing asynchronous relationships.
Our current bi-directional relationships fall short. They introduce too much friction to exploring all the wonderful public conversations on the Diaspora network (especially for new users). ��New users face a lonely, empty site. �We considered implementing the familiar follow model, but we wanted a system that embraced the asynchronous nature of a follow without losing the benefits of aspects.
For users the interaction is only slightly different:
Putting another user into an aspect means sharing with them. �Sharing includes following; you�ll see another user�s public posts in your stream as soon as you put them in an aspect. ��They, in turn, can immediately see the face that you want to present to them through your profile private posts.
Once two people are sharing with each other, the relationship between the two is exactly the same as what we currently have: �Connected people able to share privately with each other. This allows for more intimate relationships while addressing the �friction� and �loneliness� that we originally found.
For developers not much has changed:
These changes have allowed us to simplify our data model. ��We�re dropping the Requests table and replacing it with two columns in the Contacts table. �Upgrading means pulling and running a migration that will translate the Requests table over to the Contacts table. �That�s it.
For pod-runners:
Since the new model is not backward compatible (although no permanent damage can be done by contacting an out dated pod) on the protocol level, it would be good to upgrade at the same time. We are going to do it at 10 am PDT, Monday May 16th let us know if that's problematic for anyone.
During the time that servers aren�t running the same version, changes in relationships between servers running different versions won�t work, but the upgrade will clear any broken state left in the requests table.
We�ll be happy to answer any questions you might have about this transition.
Daniel & Ilya
P.S. We�ll write a blog post about this in the next couple of days.
On Thu, May 12, 2011 at 7:56 PM, Boon Kiat, Han <wj...@yahoo.com> wrote:i still think that it will require
- various ports, some minimal (communicating only the least api to not break the network)
- various hosting providers, oversight by diaspora community, to destroy the bar of entry of running server
We're definitely going to work towards lowering the barrier to entry to running a server -- both on your personal machine and on other service providers.
Our chef scripts have gotten stale lately, and they're targeted at
CentOS, which I've been dissatisfied with. I'd like to rewrite them
for Debian, or something else with an up to date libcurl.
Raphael