Hey guys
Current behaviour is: When impersonating a user’s account, the last seen date is affected by this action. This behaviour is confusing for other users and our staff since they assume, that the user was actually online at this date/time.
My suggestion is to not count the impersonation towards the last seen date.
Would appreciate your feedback on this 
I have to disagree with this. I am aware of a few forums from my communities that my friends and I have been a part of where the admins behind those forums would maliciously use ”impersonate” to try to get people into trouble.
Staff should have access to the staff logs that show when and who impersonated an account. You should make everyone on your team aware of it.
Admins could always reset that date in the database anyway, or prevent updating the last seen date using a plugin. If you cannot trust the admins then there is nothing you can do.
That’s a flaw in the system more than anything.
One thing that I think could actually help is sending a message to the user that they were impersonated. Yea, this could be undone by plugin makers but most malicious admins are usually teens that get scared by those kinds of stuff or adults that wouldn’t be really able to afford hiring someone to do program the plugin for them.
I think we’re getting a bit distracted from the subject here. The last seen being updated when a user is being impersonated is more confusing than useful.
If we need more auditing about impersonation then that’s a different thing.
By the way, I think you’re making some dangerous assumptions here.
这是我们用例的快速跟进。
由于我们话题的性质，用户非常关注隐私。因此，当一个长期核心用户（“曾经是”核心用户）突然重新出现，并且由于某些管理员冒充而拥有了一个新的“上次 seen”日期时，我们的一些用户会感到担忧或有些困惑…… 
如果您正在使用 新的模拟功能（通过将隐藏的站点设置 experimental_impersonation 设置为 true 来启用），那么在模拟用户时将不再触碰 last_seen_at 时间戳。
我们仍在计划将新的模拟功能推广到 Discourse 托管论坛。
我了解到新的模拟功能旨在降低其影响，但目前除了 last_seen_at 之外还有其他影响。据我所知，当你模拟用户时，你就是那个用户。
点击待处理的通知？他们现在已经看到了。
打开未读帖子？他们现在已经阅读了。
了解这一点后，我只会将其用于故障排除，并需要用户知情。如果用户收到通知并提供模拟会话活动的日志，我将没有意见。
好的，但是当我的最后一个 IP 留在那儿公开给那个用户看到时？当我冒充任何用户时，我的 IP 会“泄露”还是我错了？
我的解决方案是隐藏这一部分
