Based on the discussion from my thread: [image] Handling trolls with multiple accounts over VPNs Feature Hey all, we’re seeing an increase in troll users (usually users that have been suspended in the past for abusing other members) over on our Discourse forum. We can usually establish when it’s a troll account based on their email address and their source IP and deal with it, but sometimes it’s not until they make a thread with more abusive content that we see it isn’t a “real” account. I’ve already tried a few wildcard IP bans based on some DigitalOcean IPs (our trolls tend to use VPNs, most of … I decided to try my hand at building a plugin that would help prevent suspended users from returning by blocking their browser fingerprint (see panopticlick.eff.org). My plan for this plugin involves: calculating a browser’s fingerprint on plugin initialise (using the FingerprintJS2 JavaScript library) save it to the database based on the user’s id if it doesn’t already exist (there should be a single object per each fingerprint tied to the user - we capture every unique fingerprint a user logs in with to prevent access to all device in the future) on load, query by the calculated fingerprint to see if it is blocked; perform a similar action to an IP block if this is the case, or allow the user to access the site if they’re not blocked. I’ve made a bit of progress below: https://github.com/carmichaelalonso/discourse-fingerprint-bans Now the tough part for me is the fact I’m completely new to Ember and Rails, so this is taking a bit of getting used to. I’ve based this on other plugins (such as the discourse-staff-notes plugin) to help get a good structure and to learn how this stuff all works. In plugin.rb, I believe I’ve set up a model interaction layer. The model is called by the saveFingerprint function in /assets/javascripts/controllers/fingerprint.js.es6, and I’m trying to call this function (exported as an action) from the initializer fingerprint.js.es6 file. From what I’ve gathered, this is theoretically how I’d call the saveFingerprint function from the initializer: assets/javascripts/discourse/initializers/fingerprint.js.es6 master initialize() { // load external script loadFingerprintJs(function() { // generate a fingerprint async new Fingerprint2().get(function(result, components){ console.log(result); // a hash representing device fingerprint // try saving this.get('controllers.fingerprint').send('saveFingerprint', result); }); }); } }; function loadFingerprintJs(callback) { However, this is undefined (expected) and I’m not sure how this is declared. I’d welcome any input/contributions from someone a bit more experienced as to how I should go about this and how

[image] carmalonso: However, this is undefined (expected) and I’m not sure how this is declared. By default in Javascript, when you create a function() closure, you create a new context with a new this. Since your sample code above includes two function()s, the value of this will be overridden both times. An easy way to get around this is to replace your function() with the ES2015 Arrow. Having said that, even if you do fix it, the value of this in the initializer does not have a this.get('controllers') in it. You’ll need to look it up on the container, like: container.lookup('controller:fingerprint') instead. (the container is passed as an argument to the initializer).

I think that was what I was aiming to do (basing it on the Staff Notes plugin as it appeared to do the same)

Did you make any progress on this? We’re sponsoring it, if so.

Pointers for building a plugin for browser fingerprinting

Development

riking (Kane York) September 10, 2016, 10:44pm 3

Another tip: you should store the data in the PluginStore.

Topic		Replies	Views
Browser Fingerprinting plugin updates? Product Support	4	1195	January 22, 2019
Discourse Fingerprint - Browser Fingerprinting Plugin Plugin experimental	69	11005	August 11, 2026
Build a browser fingerprinting plugin Marketplace	1	1665	July 24, 2018
Route conflict on fingerprint plugin Bug fixed	3	114	September 23, 2026
Discourse-fingerprint -- what is it telling me? Product Support	7	1283	April 9, 2019

Pointers for building a plugin for browser fingerprinting

Related topics