Jump to content

Community

TSP

+Clients
  • Content Count

    6,565
  • Joined

  • Last visited

  • Days Won

    6

Reputation Activity

  1. Like
    TSP got a reaction from SSI Jake in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  2. Like
    TSP got a reaction from AlexJ in 4.4: Extend Invision Community with the REST API   
    Since the API provides means to retrieve content and user data, should it also provide a way to mark content as read? 
    Or is this already covered? (I have to admit I haven't researched this before asking)
  3. Like
    TSP got a reaction from zbahadir in 4.4: Extend Invision Community with the REST API   
    Since the API provides means to retrieve content and user data, should it also provide a way to mark content as read? 
    Or is this already covered? (I have to admit I haven't researched this before asking)
  4. Like
    TSP got a reaction from Mark in 4.4: Increase visitor registrations with Post Before Registering   
    Finally! 
    Hugs to everyone at IPS!
  5. Like
    TSP got a reaction from Farook in 4.4: Increase visitor registrations with Post Before Registering   
    Finally! 
    Hugs to everyone at IPS!
  6. Like
    TSP got a reaction from media in 4.4: Increase visitor registrations with Post Before Registering   
    Finally! 
    Hugs to everyone at IPS!
  7. Thanks
    TSP got a reaction from Matt in 4.4: Increase visitor registrations with Post Before Registering   
    Finally! 
    Hugs to everyone at IPS!
  8. Haha
    TSP got a reaction from TheSonic in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  9. Haha
    TSP got a reaction from Thomas. in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  10. Haha
    TSP got a reaction from Andy Millne in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  11. Haha
    TSP got a reaction from Matt in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  12. Haha
    TSP got a reaction from DawPi in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  13. Haha
    TSP got a reaction from Joel R in Team Talk: What would you do with $1,000,000?   
    Only correct answer is obviously to buy 1600 self hosted Invision Community Licences with all the applications.
  14. Like
    TSP got a reaction from MeMaBlue in GDPR updates for Invision Community 4.3.3   
    @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? 
  15. Like
    TSP got a reaction from Pjo in GDPR updates for Invision Community 4.3.3   
    @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. 
  16. Like
    TSP got a reaction from Sledge FTB in GDPR updates for Invision Community 4.3.3   
    @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. 
  17. Thanks
    TSP got a reaction from levsha in GDPR updates for Invision Community 4.3.3   
    @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. 
  18. Like
    TSP got a reaction from Swissgeocache in GDPR updates for Invision Community 4.3.3   
    @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. 
  19. Like
    TSP got a reaction from hjmaier in GDPR updates for Invision Community 4.3.3   
    @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. 
  20. Like
    TSP got a reaction from CrazyCalmMedia in GDPR updates for Invision Community 4.3.3   
    @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. 
  21. Like
    TSP got a reaction from Gil Ronen in GDPR updates for Invision Community 4.3.3   
    @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. 
  22. Like
    TSP got a reaction from cristian romero garcia in GDPR updates for Invision Community 4.3.3   
    @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. 
  23. Like
    TSP got a reaction from Dennis_87 in GDPR updates for Invision Community 4.3.3   
    @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. 
  24. Like
    TSP got a reaction from Archimed in GDPR updates for Invision Community 4.3.3   
    @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. 
  25. Like
    TSP got a reaction from NovaRO in GDPR updates for Invision Community 4.3.3   
    @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. 
×
×
  • Create New...