Feature Request - Delete Profile
I don't see this as an option and it's quite critical - for a user to have the ability to self-delete his profile. This should not in any way delete his wp user account (as he may still want to user other features on the site and not the community). But there must be an option for people to opt-out.
Assaf Manor And what do you think should happen to the user data in the Community like posts/comments/chat/attachments. Should it stay in the Community or be completed Deleted?
Adding related link and here so the fTeam can follow:
ability to export user data (json format) to be aligned with the European law etc.
Export option can be located in the user profile. As we know, the user may decide to withdraw his consent to the processing of data. European law requires that the user can easily withdraw consent to the processing of his or her personal data (it should be as easy to withdraw as to give consent).
Question: what will happen if we remove the user from fCommunity. Do we remove the users posts/comments completly or system automatically will change the userName to: "exUser-hash" and posts/comments/attachments can stay so we dont lose the content.
Mat, That's a good question. Not sure I have the answer right now. But it got me thinking more about privacy issues here. For instance - the fact that you can see ALL the members - not of a specific space, but of the general network is quite disturbing.
Assaf Manor, that is why the Members route and user profile data should not be easily visible especially when the fCommunity is Public. Adding related link here for disabling routes.
Other way than disabling the Members directory listing is to make it visible only to Logged users (Members listing should be limited to the Spaces scope - to the current user Spaces the user belongs etc).
Ps. I also don't know the answer what to do with user data after the user will be deleted since GDPR force us to allow user to easily delete the data etc.
Adding also adding related link with Sensitive labels idea.
In addition it would be good to limit historical data preview/search for non logged users but also in selected Spaces.
Mat, I didn't define it as public. But still - that gives people (they can just easily create an account) the ability to scrap data.
Assaf Manor, exactly - it is easy to scrape all users here and even get their emails if you think about the userNames here and public business www urls in their User Profile haha.
Members directory should be limited with a scope the user has but also if admin hide the Members link from the top menu the route should be disabled.
Don't forget that mentioning users is based on the directory so there will be a way to scrape users with some automation unless we will have randomized users IDs and Rate limits for the automation (but this is something the fTeam need to come up with so all other integrations will work smoothly without any limits).
Please read comments in this post when we spoke about UserNameAlias aka BrandName/NickName
Mat, How could you get their emails?
Assaf Manor, read this comment here.
#security-by-obscurity
Mat, I think that what they do now is use the wp user id.
Assaf Manor, yes it is based on the WP entity: WP User Name. The way to solve this is to implement CommunityUserNameAlias and use this word/string instead of the real WP User Name. If someone (Admin decision) is publishing user names in Public (especially Public fCommunity) then it is just a matter of time when it will be a problem.
#NoRiskNoFunNoPlayNoGame
Mat, No, that's not ehat I said. That the userid number itself is used as a username.
Assaf Manor, I believe the CommunityUserName = WPUserName (including ID) - it is based on the same UserID in WP DB. If you store your WP users without ID being randomized (bad practise) that it is easy to enumerate your users (if you don't protect it etc).
If you never tried and you dont protect your WP routes try this URL (you can easily loop the UserID number if its not randomized):
domain.com/?author=1
(remove the space between the / and ? in the URL) - there are other ways to enumerate users with userID=1,2,3
Try access this link below - you can change the user name with any of currently existing here in the directory. If you don't protect it then probably non logged users can also access the URL and get users data - check the url path with your domain and see what you can get in Public (if you don't protect it at all).
community.wpmanageninja.com/author/admin/
community.wpmanageninja.com/author/wordpress/