[US-31] As a user, I want to maintain multiple profiles in my Protected store and grant different followers access to different profiles, so I control what each audience sees. #11

Open
opened 2026-08-21 17:50:43 +02:00 by angie · 2 comments
Owner

@yousef mentioned: "At first thought I'm not a fan of this. It shifts quite some burden to the user.

Google+ Circles also failed pretty badly (nobody made circles)"

@yousef mentioned: "At first thought I'm not a fan of this. It shifts quite some burden to the user. Google+ Circles also failed pretty badly (nobody made circles)"
angie changed title from [US-10] As a user, I want to maintain multiple profiles in my Protected store and grant different followers access to different profiles, so I control what each audience sees. to [US-31] As a user, I want to maintain multiple profiles in my Protected store and grant different followers access to different profiles, so I control what each audience sees. 2026-08-21 18:04:33 +02:00
Owner

@jeremiah asked about "multiple profiles" user profiles or like shared folders?

@jeremiah asked about "multiple profiles" user profiles or like shared folders?
Owner

Answering to both of you:
This is low priority for me. Just wanted to mention that it is possible to have this multi-profiles feature. It was something the allelo startup wanted very much, to be able to show a different subset of information to some "circles" or list of contacts.
As we have the public store that is for everyone to see the same thing (both its homepage and its stream), we could imagine the user wants a protected version of that, that is shared only with a selected subset of their contact.
And we could imagine severla subsets like that : "family", "friends", "coworkers" ...
Technically it is done from within the protected store, by creating a new document in there of type "Channel". So yes to @jeremiah it is like a "folder". It is a document, and it has its own homepage, optional sub-documents, a stream. And by changing read permissions on this doc, the user can manage who will view and receive the updates of this channel. Could be renamed "Circle" if that's more clear.
Google+ Circle failed but the feature is still talked about and needed by some users. I won't understand the "Failure" of Google social network venture, as a definitive no for this useful feature.
Anyway, this is out of scope of the grant. But I believe it would be easy to bring it, once we ahve all the rest implemented as it is based on the same technical bits we are building.

Answering to both of you: This is low priority for me. Just wanted to mention that it is possible to have this multi-profiles feature. It was something the allelo startup wanted very much, to be able to show a different subset of information to some "circles" or list of contacts. As we have the public store that is for everyone to see the same thing (both its homepage and its stream), we could imagine the user wants a protected version of that, that is shared only with a selected subset of their contact. And we could imagine severla subsets like that : "family", "friends", "coworkers" ... Technically it is done from within the protected store, by creating a new document in there of type "Channel". So yes to @jeremiah it is like a "folder". It is a document, and it has its own homepage, optional sub-documents, a stream. And by changing read permissions on this doc, the user can manage who will view and receive the updates of this channel. Could be renamed "Circle" if that's more clear. Google+ Circle failed but the feature is still talked about and needed by some users. I won't understand the "Failure" of Google social network venture, as a definitive no for this useful feature. Anyway, this is out of scope of the grant. But I believe it would be easy to bring it, once we ahve all the rest implemented as it is based on the same technical bits we are building.
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ELFA/rfd#11
No description provided.