Jump to content



  • Content count

  • Joined

  • Last visited

  • Days Won


TSP last won the day on February 21 2017

TSP had the most liked content!

About TSP

  • Rank
    Frequent Contributor

Contact Methods

IPS Marketplace

  • Resources Contributor
    Total file submissions: 9

Profile Information

  • Gender
  • Location

Recent Profile Visitors

106,727 profile views
  1. Hi, When a device has been unused for 90 days it no longer will log you automatically in. However, unless I'm missing something, there is no cleanup done when a device has been deemed as expired. I guess there could be other reasons for keeping it, for example the device log that is now available when you view the member in the adminCP, but I would still like for the information to be cleaned up after some time. #GDPR? Maybe add an extra retention setting for this or let it be deleted additional three months after it has expired or something.
  2. If you read my original comment on the blog post, you'll see that I've already suggested using a random value, which I think would be the best approach. I also replied to someone addressing concerns regarding data mining and pattern matching. My suggestion is not to remove the current nuclear approach of no attribution for those wishing to play it supersafe. IPS could even give a cute little button next to the text input that could generate a random alphanumeric value for it! I removed my member ID sentence from the post now, to avoid any more confusion and focus on it (since it was a weak suggestion on my part)
  3. (Since the support for this seems quite substantial, with 28 likes, one "Thank you" and four supporting comments I thought I would also suggest it in a feedback topic for further discussion.) Currently on deletion of member you can choose Keep attribution as is (member name) Set it to blank (Only shows as "Guest" Suggestion: Give us an option to freely choose author attribution by giving us a text input
  4. TSP

    Outdated IPS CSS Framework

    Yeah, I know. I just feel like so many "modern designs" just go all-in on mobile, where they simply make everything bigger on desktop, even the mobile menu icon, but doesn't actually utilize the advantages of desktop size. It's like they do "Mobile only" instead.
  5. TSP

    Outdated IPS CSS Framework

    Maybe it’s just me, but to me IPS already feels mobile friendly, and mobile first. Please don’t do the mistake many do when doing mobile first, like having a mobile menu on desktop.
  6. TSP

    Outdated IPS CSS Framework

    I personally hope you'll consider changing px-values for font-sizes etc. with something less "set in stone". Like using rem-units where it can be applied or for example no unit type where it can be applied (line-height being the only one I really know about for that atm.)
  7. The Who's active-block is suddenly on 4.3 displaying who is currently using the editor / writing a post. There seems to be no built-in way to remove this, other than removing the block or removing the permission to see who's active for member groups. For any users of my plugin (Post Anonymously) for example, this is quite the privacy concern. Please make this optional :)
  8. Hi Matt, After upgrading to 4.3 I'm still unable to configure Redis with multiple readers. What am I missing?
  9. TSP

    Your GDPR questions answered

    But other parts of account history is unnesseary. For example, do you need to know that someone changed from mypreviousmail@myjob.com to unemployednow@yahoo.com for a year? You are perfectly able to make a good argument for keeping such entries for some months after the member changed it, but you're really stretching it when it goes beyond a year for some of the information they store to account history now.
  10. @Matt @Christopher Anderson Well, it's pseudonymized at least. We personally take this road, so it will be useful to me if IPS would provide the option to let us input our own value to give as the new attribution. You can argue people can comb through all of the quoted content in others members posts and get the information that way anyway, or you could argue that an advanced AI in the future could be able to figure out which users are different anyway based on writing style alone. I see no need to make it harder for people to understand how the flow of a previous conversation has been (if you choose not to delete the content in the first place), it only makes things confusing. There are 4 potential options here: Continue to attribute to Name (currently in this update) Attribute to "Guest" only (currently in this update) Attribute to the given name <Admin inputs new name> Pseudonymize: The software generates a md5-hash based on some values there and then that does not retrieve any member data, just something like a timestamp + some other value and then gives that name to all content from that account before it's deleted. @Matt Will I be able to hook into it at least?
  11. @Matt On deletion of members: Could there be an option to define the name to attribute to on that page directly? So we could input for example "Member 3312" (where 3312 would be their memberId). This will keep the discussion still somewhat reader friendly, so it would still be possible to differentiate different accounts as having written in the discussion, for readers reading old content. Alternatively let the Anonymize attribution do a md5 hash on the (memberId+some community specific value that is unlikely to be changed) and grab the first 8 letters or something.
  12. TSP

    Your GDPR questions answered

    FWIW I agree on the interpration from IPS on most points here. The only thing I'm a bit surprised by is that they don't provide retention settings for: IP addresses Account history Ironically, the "worth" of an IP address diminishes the longer it's stored, but I still feel this is one thing it would be appropiate to have a retention setting for. I will likely make a custom script for this in my case which will likely operate with two retention settings: One for members who have NOT been warned and/or suspended the last year One for members that have been warned and/or suspended the last year
  13. I've also encountered some weird behaviour here, although I dont have any child/parent themes. I haven't really cared to investigate it much, but it seems that the first theme upload new version (after an upgrade) usually misses some things, especially if it does that thing where it asks you which version you want to keep... (even when no changes have been done between the previous upload and the new one) So after every upgrade where I've made updates to the installed theme, I usually just upload as new version twice and then reset all cache. When I havent done that it has usually resulted in problems, but when I do it twice like that, it seems to go okay.
  14. I guess my most nerdy disposition is that I like to read through plans for and follow railroad projects closely. I'm a huge supporter of more rails transport! Other than that it's mostly theatre (acting) and Netflix.
  15. I agree with the original request. Update the time for last visit (or save it in another field) and simply hide that information on the profile if the last time they visited chose to log in anonymously. Or show the last time they logged in publicly. The current way screws up statistics and for example bulk mail sendouts. Disabling anonymous logins doesn't help, as the feature of then logging in anonymously is removed...