Issues with public/private followings

[miguelfreitas]

Issues with public/private followings

[toyg]

While the system is young and lacking content/users, I think public-by-default is actually the better choice. I agree that the wording on the button should be "Make Private" / "Make Public".

[BlockTester]

@toyg the problem is that once it's public there is no real way to revert back to private (some people might have had access to the information) at the very least it needs to be a user option.

[toyg]

Fair enough.

[BlockTester]

It also appears that the button's state is not updated when loading the followings page, there's no real way to know if a following is private or public other than logging in to another account.

[miguelfreitas]

You are right. When you start as public someone may see your DHT update even if you remove it later. I also agree UI needs improvement.
But starting as public definitely helps get people connected, as it is the behaviour they are used to.

What about implementing another access to follow users privately from the start? Perhaps from the following page where we have space.

[BlockTester]

I agree that starting with public followings is good for the network at this early stage, but I think it is very confusing to users. It would be even more confusing if depending of where you click follow it is a private or public follower. What I think would make the most sense it to have a global user option "Make my followers public by default". It would be easy to turn on and off. For now I suppose it could be turned of by default, while documenting somewhere what that means to a user's privacy.

[miguelfreitas]

Good solution (config page with global user option), i like it!