# Topic\_views vs Topic.views **URL:** https://meta.discourse.org/t/topic-views-vs-topic-views/97175 **Category:** Development **Created:** [September 14, 2018, 8:25am UTC](https://meta.discourse.org/t/topic-views-vs-topic-views/97175 "2018-09-14T08:25:31Z") **Posts on this page:** 1 **Showing post:** 9
### Author: ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans) #### Post date: [September 28, 2018, 8:55am UTC](https://meta.discourse.org/t/topic-views-vs-topic-views/97175/9 "2018-09-28T08:55:03Z")
> [@GDPR countdown and compliance](https://meta.discourse.org/t/gdpr-countdown-and-compliance/87190): > > As we’re quickly approaching May 25th, here’s my (perhaps naive) understanding of certain key Discourse GDPR issues: Right to Be Forgotten white_check_markIf the user requests, the admin can use the user info panel to delete all of a user’s posts. Note you may need to up the “delete user max post age” and “delete all posts max” settings but then it’s possible. Once there are no more posts you can then delete the user. Alternatively, a less disruptive solution is the “Anonymize User” button … > [@Problematic IP address fields](https://meta.discourse.org/t/problematic-ip-address-fields/83785): > > Continuing the discussion from [Providing data for GDPR](https://meta.discourse.org/t/providing-data-for-gdpr/83595/17): I did a first pass over Discourse’s tables, and I found several places where IP addresses are being accidentally correlated with user IDs. This is toxic data generating liability for Discourse forums. List of problematic IP address fields: white_check_mark x incoming\_links: stores timestamped IP address correlated with user ID and an exact post ID, topic ID, and Referer: header Fixed Storage: PR#5826white_check_mark … It’s already discussed in above topics. --- _[View the full topic](https://meta.discourse.org/t/topic-views-vs-topic-views/97175)._