Privacy Concerns in the Spaces Product Architecture
In relation to the #Spaces product, the concept is clear: this module enables users to organize groups, called Spaces, in a nested hierarchy, where each ‘Parent Space’ can contain multiple ‘Child Spaces.’ This structure allows for extensive customization and flexibility in organizing content and groups.
However, this arrangement brings significant privacy challenges. Each Space comes with its own permissions and member controls, allowing users to manage their access at every level. While this offers flexibility, it becomes problematic when the names and links of these Spaces appear in autocomplete search results. If a secret or closed Space, intended to remain confidential, is included in search results, it undermines the core principle of a private space.
The module’s ability to support Communities and Sub-Communities is a valuable asset. For instance, on a platform dedicated to International Soccer/Football, a Parent Space could represent countries, while Child Spaces could represent individual teams. Users following a country could be automatically enrolled in related teams but should retain the option to follow only specific teams.
To uphold privacy within Spaces, all content and associated details must be accessible only to the creator and invited members. If such content becomes publicly searchable, it defeats the purpose of having private or secret Spaces. Ultimately, for the Spaces module to be effective, sensitive information must remain protected, and the principles of privacy must be respected.
According to the Cambridge Dictionary,
"If something is secret, other people are not allowed to know about it."
Therefore, if the titles of secret spaces and their content appear in public search results(even for unregistered users), they are no longer secret, and the definition of a secret space and secret content loses its meaning.
-
Curious, did you perform these tests on a standard account or did you do this from an operator account with a standard membership profile?
Yes, this matters. Hence why I'm asking.
-
I have the same experience with Person profiles. Also I have set the name and profile picture of private profiles on hide for public. They still appear in search results and the cover meta is not accurate to the privacy or individual settings (full name and profile picture still appear)
It would be nice to have future form/display settings for cover metas.
-
When I write 'public' it means you don't even have to be logged in, you're anonymous but you have access in the search results of secret spaces, and secret content names, try it yourself to see.
-
Hello all!
I've checked the space search in the parent space field during the creation and in the leyword search. Well, in the first case, I couldn't reach the closed and secret spaces there. And in the second we have now the complete hiding of the secret spaces.
I guess it is the fine level of privacy for now.
-
Please check the autocomplete search field; you will notice that the titles of posts from the secret space appear directly in the search suggestions. Who would want the names of secret documents to be visible in the search suggestions? Any user who is not logged in can view the names of document posts in the secret space. This means that all document name post in secret spaces are public, for anyone, whether it's a person or a search engine or a bot. Also the header image of the secret document is public in search suggestion so the claim that these spaces are secret is just a joke
Only those with access rights should be able to search for the document by name. Also, if the posts are secret, an encryption method should be used, just like for passwords. And only those with access rights can read them. That means a secret.
also the name of the document should not be written in the url address https://www.exemple.com/view-post/visible-name-of-the-secret-document it should be a meaningless string randomly generated.
browser console:
<div class="bx-def-unit-info flex flex-col pl-2"> <div class="bx-def-ui-title">Visible name of the secret documentdiv> <div class="bx-def-ui-type bx-def-font-meta">postdiv> </div> -
-
