YOU’RE THE BEST, THANK YOU!!!
And they say bullying doesn’t work.
I am glad you are trying it. Fingers crossed.
@ForTheFallen I asked behind the scenes if you are thinking you missed something.
1 Like
Nice, +1 here for Firefox users who would be excited to try this extension out!
i did 
but made the assumption after scouring the threads. thanks!
1 Like
The Firefox version was approved.
2 Likes
Look at you submitting to bullies and gaining a second version out of it.
Now, how to convince you it is also VERY easy to put this in the iPad App Store for safari on the iPhone and iPad.
Seriously, it is.
3 Likes
Thank you!
Thank you so much!!!
This is perfecet!
1 Like
Here’s a weird one for you: models uploaded before the latest change to the point/reward system may be tracking for an increment of x25/x50/x75 instead of just x00.
For example, my Fidget Cube: Angled model gets rewarded at 76775/76875/76975/etc.
The result with the extension right now is that it shows the wrong target (currently showing 76700) and the progress bar is empty. This is the case on most of my models which predate the point/reward system change.
It’s because the plugin can’t get an accurate reading from the rounding up of downloads by thousands rendered on the page, so it thinks you are already on a reward point threshold.
Ahh, gotcha. Thanks for the reply + explanation.
Yep, sorry. I think I could poke at their API and get an accurate read, but I’m reluctant to use undocumented APIs I am not supposed to be using… I’ll ponder 
Public bullying this time.
How about adding your magic to the model pages?
I think @Hollandje beat me to it.
Hah, yea. I use your extension for the user pages still. I might at some point also add the feature to my extension but yours works totally fine for the time being 
Version 0.8 includes this change and it’s been published for Firefox and Chrome. I expect this to break at which point someone else (Hollandje!) can take over this project 
1 Like
First of all, I would like to let everyone know that this post isn’t meant to attack or question the intent of the OP but rather a reminder to everyone the risk that any code/program have negative potential including browser extension/plug-ins. I debated over several days whether to post this or not and was hoping that someone else would beat me to it so I don’t have to but since nobody did yet, I’ll post this then.
While I do not doubt that the OP’s intention is noble, i.e., to provide a helpful tool for MW designers, I feel that there is potential for malicious use of the extension’s code. Might not have occurred to the OP’s mind but sooner or later someone else might.
Just like everyone else, I installed the extension so I can try its functionality and evaluate first before posting this. I agree that there’s utility for such an extension. My understanding is that the data used by the extension is gathered through an API that returns the download counts and calculates the remaining downloads for the next point drop. That’s well and good and the standard. However, other data in the page are available for browser extensions to scrape, including gift card codes. A bad actor could take this extension’s code and modify it so that gift card codes are read and sent to a remote site without the user knowing. I checked my Redemption History page and the gift card codes are not encrypted, very easy for an extension to read and send out to a remote server. At the moment, there’s no way to delete gift card codes from history, something I have expressed to MW already since it’s a huge risk if one’s MW account is hacked.
OP - I commend you for the idea and the great work that went into this. People will be putting trust in you that the extension will behave within the confines of its purpose especially with the extension running within account pages with security and authentication already bypassed.
Everyone - pls be reminded of the risks before you install any program, plug-in, etc.
3 Likes
That’s why I love open source! in case of @Contributing_Factor’s plugin I can easily go to GitHub - ContributingFactor/MWPointTracker: Chrome extension to display earned points on MakerWorld and read the code of content.js to see whether anything nefarious is there.
This is true and one of the main reasons why in mine I don’t have the code auto check for gift card value and blur automatically or do and read api calls. It is always a risk you take with extensions like this, even having it open source won’t be a 100% safe option because one could just simply not push the update to GitHub and push a malicious update to the Chrome webstore. Sure if you check manually with every update you can avoid it, but many, including myself, don’t.
One does need to declare whether or not there are outgoing connections and why you need them on the developer dashboard which triggers an extra review from the Google webstore team but what was seen on the recent debacle with the editthiscookie extension I don’t know how strict they are.
I personally can say that I have no bad intentions and just find this a fun side project to work on but that will honestly always just be my word against others. I do get why chiz_m is mentioning this though, hence I already indirectly address this concerns on my own thread by mentioning the no auto check and manual blur of gift cards.
Content.js (the brains of the extensions) of my extension can be inspected on the homepage of makerworld through the developer tools in Chrome without putting your gift cards at risk because of the dynamic nature of the makerworld website.
Life requires assuming some level of risk and worry. It’s up to every user to weigh risk vs benefit.
The extension does not collect any data. It passively reads the page you are currently on and modifies it on the fly by inserting the new elements. There’s no code in the extension to read anything except the number of downloads and prints.
It does not connect to any external servers or issue any api queries to the MW servers. And it does not gather or save data anywhere.
The plugins are reviewed and vetted by both Chrome and Firefox scripts and reviewers. So pushing malicious extensions to either stores and getting it past that would not be trivial and would require much more code obfuscation.
You should not install things from GitHub unless you can read the code and ensure it does not do anything shady, or have some other guarantee of its safety.
4 Likes