Hi Rosemary, Thanks for the COPPA update. Can you call out the cavalry on the eve question shark forum? There are a bunch of us whose entire websites and forums have been down for an hour without response from social strata. Thanks so much.
I think the basic age limit should be raised to 18. Just had a high school senior friend me on Facebook simply because I graduated there 25 years earlier. I seriously doubt that she would really want to hang out with a 43 year old truck driver.
You're welcome Lynda! And the cavalry resolved the issue yesterday...I'm looking to improve our outward communications when things like that happen; we'd like to be much more proactive than we were yesterday, and I'm sorry for that. Harold, I might agree with you. It's kind of funny that the actual age issue never really came up in their discussions. It's probably because there are certain situations where you wouldn't want to lock out 15-16 year olds.
The conversation about kids online is an interesting conversation. Sometimes it is tricky to navigate these waters. Do you guys staff an ip lawyers or do you use one from the outside. I would be interested to see how small businesses handle these issues.
Thanks for the updates Ted and crew. Regarding: "Extract Improvement: we now filter out quoted text from content extracts to make the extracts more readable." Can you explain this one a little more?
Hi @neil ! That just means that when Hoop.la generates automated extracts of posts (e.g. for showing recent replies in the topic list), Hoop.la will now strip out any quoted text (i.e. text in a blockquote ). This will give more focus to the actual post/reply/comment that was made.
Hi Ted, I'm guessing this is not possible, but it would be great if we could use Circles to apply the GDPR settings only to members to whom it applies. As it stands, we're telling clients in Europe that they will have to drop membership if they want these features, because we are not willing to enable these restrictions for everyone when less than 1% of our clients are in Europe. If we had the ability to have a Europe Circle, and only enable this for them, that would be ideal. Thanks, Mary
Hi @MHK@CS2 , there's currently no way to set permissions up or use recipes as you've described. I'm not a lawyer, but I'm not even sure that approach would work from a GDPR perspective. You would technically need to identify members by first collecting some information about them in order to determine whether to give them the "GDPR treatment" or not. I'm not sure that would pass muster. It's definitely an interesting idea, so you could always suggest it separately in the support section of...
Hi Brian, I understand what you're saying. We're in a different situation than most of your clients, I believe. Our community is 100% business related; all members are paying clients and they engage us to provide jurisdiction-specific regulatory information. Members cannot join our community on their own - they have to execute a contract for our services first, which includes agreeing to our terms of use of the community. Our members are chief compliance officers of (highly regulated)...
My best recommendation would be to consult a lawyer about what your GDPR requirements are. If you are not doing business in the EU or directly marketing to users in the EU, you may not need to comply. You also might consider your specific workflow. If these users are doing direct business with you, you could make it clear in your separate onboarding / contracting process that their personal information will need to be used in your internal system (Hoop.la) as a contingency of being a...
When you block a person, they can no longer invite you to a private message or post to your profile wall. Replies and comments they make will be collapsed/hidden by default. Finally, you'll never receive email notifications about content they create or likes they designate for your content.
Note: if you proceed, you will no longer be following .