NGL's click counter is FAKE.

2025-02-24T04:35:49Z

warning: some profanity is used in this post

I was messing around with NGL.LINK and noticed a little counter:

This counter intrigued me, so i popped open inspector, and what do you fucking know, there's no data. This is the code snippet we are interested in:

  setInterval(() => {
    let clickCount = parseInt($('.clickCount').text()) 
    clickCount += Math.floor(Math.random() * 5) - 1 
    $('.clickCount').text(clickCount)
  }, 800)

The setInterval line is the start of a recurring timer, if you look to the end you'll see it says "800", so every 800ms we re-run the code. What does the code do though? It first, pulls in the text of the .clickCount HTML item, which is the counter, then it uses parseInt, a function that, if a string is only a number, turns it into a proper integer so we can perform mathematical operations on it, after that we save it as clickCount (a variable) in the next line down we increment clickCount (the variable) by Math.floor(Math.random() * 5) - 1, what exactly does this mean? First, we run Math.Random (order of operations and all that jazz), this throws an output like this:

We then multiply that by 5, so it atleast, some of the time is at-least 1, we then floor it which basically strips away the decimal values, and then subtract by one at some points, which could theoretically be dangerous if it ends up being a 0.9999 or whatever which means it would take an item away, finally we write this value back to the element, rinse and repeat. I leave you with one thing:

An Addendum: Unclicking?

I noticed this code has the possibility to SUBTRACT from the counter, so i ran it manually, interestingly NodeJS and my browser (firefox) reported different answers, see for yourself. Ignore the void function wrapping it in node, for some reason node likes printing extra garbage and i had to void the trash.

NodeJS

Node seems to have a habit of rolling zeros and negative values, which when negatives are rolled, it would seem like a user "unclicked" the button.

Firefox

Ok, but WHY THE FUCK IS NODE ACTING DIFFERENT TO FIREFOX??? Now I gotta test it in Chrome >:3

Addendum 2: Electric Boogaloo (2026-02-23)

Just found a backup of my old site and had to put this post back up.

Also fuck you if you have any of the following on your site:

Fake countdown timers
Fake scarcity information
And ofc fake click counters.

StepSequence: A marvelous in browser "sequencer"

2025-01-10T10:26:00Z

(sorry! The volume was really quiet in OBS or something)
a preview of the application, showing an example melody created by yours truly

What now?

Step Sequence is a basic sequencer tool by Kevin Macleod (yes, the dude who makes those iconic royalty-free tracks also makes software), it is by far my favorite web based song creator, it sure isnt advanced by any means but is simple, somehow even simpler than Chrome Music Lab but is no where near as advanced as something like Online Sequencer

How can I try it?

Grab anything with a browser. Go to: https://danger.academy/step/

Drawbacks

It works using Midis, so you're best recording your screen and extracting audio that way as when played outside of StepSequence its up to your system to decide how it sounds
It has no import function to reimport previous tracks

Blog Title