Hey AlexT, thanks for your reply. I understand what you are saying about the overall visibility of the timeline and that is not something that we are looking to change. We want people to see and know how others are interacting with the site. However, for our implementation of Dolphin and what we are trying to accomplish, it does make sense to initially set the portion of timeline where users can interact on anothers timeline by being able to "Write", "Share a link", "Share a Video", etc. is initially set to "Me Only" and not to "Public". This gives that user the choice to allow others to put something on their timeline. Initially, we don't want another member or friend to be able to post on someone's timeline without that user's approval.
The only way that I can see to do that is to set the posting portion of the timeline to default to "Me Only". However, that's a manual change that the user would have to know to do and I'm looking to find some help on how to change that section of the timeline or set it when someone joins to that "Me Only" privacy setting.
What I've been told and read so far is that privacy is inherently defaulted to public as Dolphin simply reads the privacy table. If there is no record in the privacy table then it's public. At this point, there would be no record because the user hasn't changed it and another user would be able to post on their timeline. If there is a record for that block and that user in the privacy table then Dolphin reads it and applies that setting for that specific block.
Problem is that would mean every user would have to go in and set that versus's an overall admin type setting or code modification.
So far, the only solution that I can come up with is to just build another cron that runs every hour or half-hour that would look for new users and simply insert that record for that user_id and block_id into the privacy table (sys_page_compose_privacy). Although not the greatest solution as someone "could" possibly catch a new user and post to their timeline, it does stay out of the core code and should work.
A better solution would be some kind of overall admin privacy setting or hook that could be deployed to interact with the join process that does this same thing.
Again, thanks for your reply and I do appreciate your input, but for us and our implementation it does make sense and we are just trying to figure out a way to stay out of core product for future growth. As a matter of personal opinion, thus far I really like Dolphin, but I think a more broader/bigger picture approach could be accommodated in the means of admin control and setting for each feature/module baked into the product and published as core other than templating and css could be accomplished.