Forum Activity for @researchcooperative

Creating Open Graph tags with Meta Tag Manager in JR

Using Jamroom

JR Documentation has a good step by step guide for using the meta tag manager.

This led me to check my site using the Facebook "Sharing Debugger" page (rude as that may sound).

I added og:url, og:title, og:type, etc tags to my site, reset caches, went back to Facebook, asked for my site to be "scraped" again, then found that the changes had been made.

But then, in the Facebook Debugger warnings panel, I see this:

Tag specified as 'name' instead of 'property'. The following meta tags are specified using 'name' instead of 'property' and will be ignored unless specified using the 'property' key: og:url, og:title, og:type, og:description, og:image

Hmmm... in Meta Tag Manager, all the Open Graph (og) items are listed in a column called "Name". There is no "Property" column for the og items.

Does this mean I cannot actually make effective Open Graph tags?

Or is there actually no problem, and the Facebook Debugger warning can be ignored?
updated by @researchcooperative: 09/02/18 11:57:49AM

Are tags on profile pages expected to be displayed in the comment wall?

Using Jamroom

On my site, tags on profile pages are displayed inside the comment wall and are not visible to visitors who are not logged in. See the screenshot.

I want them to be above the comment wall, and to be visible to all visitors. This is important to maximise member-to-member connectivity throughout the network.

I am happy for comments on profile pages to be visible to logged in users only, but is there any easy way to control this?

How are tags displayed on profiles in other networks?


updated by @researchcooperative: 08/28/18 11:00:35AM

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom


This looks excellent to me... it creates an opt in at the first step, separate from other issues, and actively encourages new users to take control of their own account.

On the matter of when accounts should be deleted, after last login, I received feedback from several members on this question, and the average waiting time they suggest is 2-3 years. If the process can be automated to some extent, it can be explained in the Terms of Service. Probably best not to give yet more options for users already overloaded with options (contrary to my own suggestion above).

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

I think JR has had a basically good system pre GDPR, but the new requirements are:

"For consent to be valid under GDPR, a customer must actively confirm their consent"

and

"Under GDPR, email consent needs to be separate. Never bundle consent with your terms and conditions, privacy notices, or any of your services, unless email consent is necessary to complete that service."

My interpretation of the above is that setting up an account with an email address gives Admin permission to complete the account registration as a service (see Strumelia's question above) but is not a separate, explicit consent for further ongoing communication.

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

I wonder if part of the notifications settings, a nuclear self-destruct option could be offered:

Delete my account and all content if I have not logged in for more than 1 or 2 or 4 years (requires Admin. review if you have posted images or text). Admin review gives Admin a chance to keep valuable content with your permission. Default = 4 years (or other period according to Admin. wish).

Something like this might (1) help make us GDPR compliant, (2) reduce cholesterol accumulation in the arteries of our network, and (3) make Kickbox validation of account email addresses redundant, since someone who changes their email address might be an active member who has not yet updated their account email address.

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom


I think/hope we can assume that sending out an email with activation/login link, during the signup process, is acceptable practice!

Perhaps the account activation email can have a message that highlights the need for new members to opt in to receive further communications from the network without logging in.

And "Receive notifications to my online account only" needs to be an easily found option in the notifications page..
updated by @researchcooperative: 05/25/18 04:49:56PM

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

Here is a good summary based on the ICO information:

https://litmus.com/blog/5-things-you-must-know-about-email-consent-under-gdpr

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

GDPR requires consent to receive an email to be opt in.

JR currently offers an opt out for all notifications, rather than an 'opt in' , and the default for specific notifications appears to be "send email".

Send Email = Send Private Note = no difference?

Private notes are forwarded using the registered email address (unless there is a setting for storing and seeing them online only, the way that online bank services do).

Why not just reduce both of these to "send email"?

Can the search box for group members do more than finding member usernames?

Suggestions

Thanks, good to know.

This is something I might eventually request as a paid customization for my skin.

The GDPR right to be forgotten - applies from May 25th 2018

Using Jamroom

Today(22nd May 2018) I received this notice from an internet service that I signed up for about four years ago and never used:

"The European Union passed some wonderful rules to protect privacy: GDPR. It requires that all services limit the length of time they keep inactive accounts on their servers. While this law is only meant to protect European residents, we’ve decided that privacy is something everyone should have."

etc.

(GDPR = General Data Protection Regulation. It is well explained on Wikipedia.)

The company wants me to renew my account, but will delete all my old data if I don't ask for the renewal. (I'm not renewing).

1. We had a discussion recently here in JR (sorry, I have not found the thread yet) about how to automatically identify inactive members and then eventually delete them. Now it seems this is something we should do by law, if we are operating within Europe, or want to be compliant with European law for our European members.

So we do need an automatic time-limited membership system, and the time point for reference should be when someone last logged in. If they have not been active for a long time since that point (e.g. 2-3 years?) then they need to be shunted to a quota where the data can be reviewed, and the accounts deleted. We also have to make sure that old personal information is deleted from system backups.

2. With Kickbox, we can already identify and move accounts with invalid email addresses to a private quota, where the profiles are not visible online to site visitors and users.

We cannot delete the holding quota until all accounts in the quota are deleted, and we can only delete those accounts one by one, which is tedious for hundreds of old accounts. Seems like I will have to do this though.

3. For situations (1) and (2), it would be useful to be able to select all accounts that had their last login at a certain date or further back in time, and then delete them all, and have that happen in the backup system the next time a new backup copy is made.

Anything else I should be forgetting?
updated by @researchcooperative: 08/27/18 08:07:58AM