Forum Activity for @brian

Oauth2 request from listener

Jamroom Developers

You can do anything you want in a listener - you can request the token via a request, then turn around and make another request. There's no restrictions on what you can do in a listener.

User Privacy Controls - More important now than ever

Suggestions


This is content related - not really Jamroom. It's up to you to police the site content on your site.

Creating Open Graph tags with Meta Tag Manager in JR

Using Jamroom


I am not sure what you mean here - all JR templates can use $variables.

Something off with pagination

Jamroom Developers

This is actually expected behavior when using "simplepagebreak".

Mountaintop has posted exactly 50 topics. With simplepagebreak being used (instead of the normal pagebreak due to the size of the datastore and the "Use Optimized Pager" setting enabled in the Core), there is no "total" SQL query that is run to determine the total number of posts. The counting SQL query used with the regular pagebreak is the slowest part of the function, so we exclude that when using simplepagebreak and just assume that if we can fill an entire page to it's simplepagebreak number, then we always show the "next page" link. In this case if Mountaintop had 49 or 51 posts this would not be an issue, but since he is right at 50 we show the "next page" link even though there is no next page.

This is an acceptable side effect for % of time you run into it versus the every-request drastic performance improvement you get from not running the counting query.
updated by @brian: 05/28/18 08:37:19AM

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

Using Jamroom


Because you can set notifications to be Private Note, then disable Private Note notifications - that way you receive no email but all notifications will be in your private notes.

It sounds like we need a control in the User module to set all notification options (by default) to "off".

User Privacy Controls - More important now than ever

Suggestions

How do you ensure the user is putting in their real date of birth? If you really must be sure, there is only 1 way to do it:

1) Make ALL accounts admin activated only
2) Require the user to send proof of birth date to you via mail or a scan before you activate their account

Anything else leaves room for someone to lie to you about their birth date.

To be honest this is an area that we've not looked into much since no one wants it - in fact I think you're the only one to ever bring up concerns about age related content. Since our development is primarily driven by what users ask for, it's not an area we've focused on. Now with the GDPR that may change, so your feedback is appreciated

GDPR?

Using Jamroom

See my follow up here:

https://www.jamroom.net/the-jamroom-network/forum/new_posts/58375/the-gdpr-right-to-be-forgotten-applies-from-may-25th-2018

I'll be honest - I'm not a GDPR expert, so let me know if there are any questions about how JR works in regards to GDPR privacy and if needed we can check it out.

Proxima Invalid Item owner

Proxima

You should not get an "invalid item owner" if using the master key - I will check that out.

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

Using Jamroom

Just wanted to add here that Jamroom is (as far as I can tell reading the GDPR requirements) already mostly GDPR compliant. The only thing a site might want to change is their Privacy Policy and Terms of Service to use more appropriate "GDPR language".

The only thing we are working on right now is an update to the User module that allows the site to change the "notifications" tab - this allows you to pick whatever format may be easier for your users, since a lot of the GDPR is about making it easy for a user to see HOW they will be contacted and how their data is used.

Note that the data retention period for the GDPR is (as far as I know) still a gray area - I do not believe you have to automatically delete a user's account if they have not logged in in X days, but instead you just must make it easy for the user to delete their account and in turn have it delete ALL their data (which JR already does).

Let me know if that helps or you know of a GDPR requirement that needs support on our end.

Thanks!

Activity Timeline Question

Design and Skin Customization

Yep - exactly. You can string as many values as you want on the not_in - i.e.


So you're not just limited to 2 values - you can have 20 if you want.
updated by @brian: 05/19/18 12:05:53PM