For security reasons, we intentionally restrict access to conversations on social objects. OSN does support public conversations, but it does not support public social objects.
There were plans to relax those restrictions, and leave it up to the social object owners to decide whether the conversation should be private or public, but those plans have been shelved for now.
Thank you very much for your reply.
In your knowledge, has an ER been raised for this issue?
The big advantage of OSN over e-mail is that conversations are visible for people even if they were not in cc (in e-mail).
I would think it makes sense to restrict people from conversations on social objects they do not have access to, but I don't see the point in restraining them from public conversations on social objects they can access.
Removing this restriction would make OSN so much more beneficial and user friendly, don't you think?
The problem was that not everyone who has access to the social object necessarily has access to the public conversations. Outside Users, for example (e.g. Partners). But I think what you are asking for makes sense. There already is an ER for the feature, but you are welcome to create another one; especially if this is driven by a customer use case.