A peculiar issue where notifications are being sent displaying the receiver’s username as the action performer.
AI-generated summary
The discussion revolves around a notification issue where the recipient’s username is displayed as the action performer. nexo shares an image of the issue and mentions being on the latest Discourse version. supermathie asks about the version and plugins, and nexo shares the version (v2.3.0.beta3 + 38) and a list of installed plugins.
nexo tries running Discourse in safe mode, but the issue persists. codinghorror suggests the issue might be caused by a rogue plugin, but nexo mentions that disabling all plugins in safe mode didn’t resolve the issue. Falco clarifies that safe mode only disables frontend plugins and that notifications are generated on the backend.
nexo decides to disable plugins one by one and Falco notes that removing plugins won’t affect existing notifications. nexo tries retriggering notifications by liking different posts. Stephen suggests disabling all plugins first and then reintroducing them. Ultimately, nexo discovers that the Follow plugin is the cause of the issue and requests @angus to look into it.
Is your Discourse version up to date?
What version are you running?
I’m on the utmost latest version of Discourse.
Any resolution/thoughts?
What version on you on?
What plugins do you have installed?
Try running discourse on safe-mode and report back.
I went into safe mode and am updated to the latest Discourse version. No luck. Anybody else experiencing this?
Almost certainly a rogue plugin. All third-party plugins are potential causes.
But I went into safe-mode and disabled all plugins and the same issue persists. 
Oh, I see. I’ll continue to disable plugins one by one (without entering safe mode) till I find the issue.
Also the notifications are generated once and store in the database. So removing plugins won’t make this old one revert.
Yeah, I’m just liking different posts to retrigger a new notification event.
Disable them all first to make sure it’s not something more fundamental, then reintroduce a few at a time.
Fixed! The Follow plugin was the cause of this - @angus could you look into this? Thanks to everybody.