The plugin used to gather all users using the same IP address without manual searching. But this has stopped working now, and I can only find out by searching.
1 like
I just upgraded Discourse and see a message now:
[Admin-Hinweis] Eines deiner Themes oder Plug-ins enthält Code, der aktualisiert werden muss. (ID:discourse.deprecated-resolver-normalization)
And in developer console:
DEPRECATION NOTICE: Looking up 'route:admin-plugins-fingerprint' is no longer permitted. Rename to 'route:admin-plugins/fingerprint' instead [deprecation id: discourse.deprecated-resolver-normalization]
2 likes
Following up on the deprecation above.. on current core (v2026.8.0-latest.1) it’s not just a warning any more, the report page itself looks broken.
/admin/plugins/fingerprint comes up with an empty “latest matches” and flagged list, and the console throws:
Uncaught (in promise) TypeError: Cannot convert undefined or null to object
at Object.values (<anonymous>)
at fingerprint-report.js:58
1 like
My imaginary friend and I tried around a litte bit and came up with two changes for this plugin. One for the deprecation notice and one for the JS error in the development console of the browser.
I would like to ask you to take a look at this. I can’t really program.
If the fixes are okay I can do a PR. If desired.
2 likes
I usually spoof my fingerprints; how will it treat folks like me? I promise I’m not a troll 
Asking because I’m with the privacy tribe, and they are usually very respectful of discussion ethos but do not want to give their data everywhere and every time.
I don’t see browser fingerprints as a real threat to privacy. I’d rather have tools to protect against botnets, spoofed fingerprints, scrapers and DoS attacks than focus on alleged privacy. As a site operator, that’s a real threat for me.
Well, in EU fingerprinting is considered as a real threat, and that’s why it is forbidden.