'tH3 Awsum' Neobux Emporium..

Update:
It seems that userscripts.org have updated their certificate and the problem has stopped.

Quote:

Quote:

Quote:
kwah any update available ? …. the userscripts.org certificate it`s expired … thanks

I don’t understand.

I was away from my computer over most of the weekend but I did get two minutes to check out userscripts.org on my phone and saw no problems. Perhaps you could explain a little more?

kwah, read:
Expired Script Certificate
godaddy certificate expired

Everytime I visit Neobux I get this message:

userscript.org:443 uses an invalid security certificate.
The certificate expired on 21/03/2010 09:24
(Error code: sec_error_expired_certificate)
This could be a problem with the server’s configuration or it could be someone try to impersonate tge server.
If you have connected to this server succesfully in the past the error may be temporary and you can try again later

Can someone help me? I got this message today when I visited Neobux.

BTW: I use firefox 3.6

Short Response

That is clearly a problem with the userscripts.org SSL certificate and not my script – note the mention of port 433 in the error message, the default port for https / SSL. The ‘correct’ fix for this is for userscripts.org to update their certificate but this would be beyond my control.

More detailed Information::

My scripts check for updates using the https:// (secure) version of the download links, but because the userscripts.org SSL certificate (Secure Sockets Layer – the thing that triggers the ‘secure’ padlock in the bottom right of Internet Explorer) has expired, your browser is unable to verify that the site is actually who it says it is.

This causes an error whenever the script tries to check for updates because the browser will not allow it to ‘see’ what is at the https:// link. This causes the update to fail and the script then keeps retrying on every page load (and causing the error to popup).

Check below the fold for the fix =]

(more…)

With only two weeks to go until I go off to Australia for a couple of months, I figure I should try and get some updates out to all my adoring fans ;)

So…. for starters, I’ve just uploded a copy of my current progress in rewriting the Neobux Referral Highlighter script.

Everything is looking fine and dandy with it for now but I’ve decided to upload it as ‘Experimental’ (read: pre-release / beta) because it hasn’t been tested very thoroughly and may still contain bugs.

New Features

The biggest change that you’ll see as a user of the script is that you will be able to define your own custom rules about what you want to highlight referrals for.

For example, have you ever wanted to completely ignore referrals that are new & haven’t had a chance to ‘prove themselves’?  Or perhaps you want to highlight different referrals different colours based on different averages depending on how old they are. Well now you can*.

*- You just need to be able to create a ‘rule’ for it ;)

(more…)

Intro

Following my previous (less than adequate) experiences with Neobux support staff I am now reduced to contacting them again. Fortunately this is about a seperate non-critical issue but it is one that has bugged me for a while now (in fact, the first time that I reported it was ~3months ago, before Christmas).

Anyhow, to the actual issue:

The Problem

The problem is regarding the ‘Total Number of Referrals With Scheduled Payments For the Next 90 Days’ graph in the referral statistics page being one day out. I shall let my forum message tell the story:

Posted by: kwah

Date Posted: 2010/02/28 at 00:19

Message:

This is a problem that I vaguely remember mentioning before but had never gotten around to posting about it in a topic of its own..

Anyhow, I’ve been getting a little bit behind with my renewals recently and yesterday I noticed it again…

Long story short, the graph showing the number of referrals due for renewing appears to be inconsistent with the ‘true’ number:

This screenshot was taken on 26/Feb/2010 at 13:45pm local time / 08:45am server time (same date):

I have annotated a screenshot of the mass-renewal page (grouped by minutes) to what I believe this data shows:

It is curious that though the screenshots were taken ~1min apart, the times due are 2mins apart (I only just noticed this)

Long story short, I have this many referrals due for renewing:

(local time)
* 0 refs expire ‘today’ (26/Feb/2010)
* 1 refs expire ‘tomorrow’ (27/Feb/2010)
* 8 refs expire ~two days away (28/Feb/2010)

(server time)
* 0 refs expire ‘today’ (26/Feb/2010)
* 2 refs expire ‘tomorrow’ (27/Feb/2010)
* 7 refs expire ~two days away (28/Feb/2010)

(I have listed both local/server time to make it very obvious that it is not a time difference issue)

This is inconistent with the ‘grouping by days’ page and the referral statistics pages, however:

I have tested this recently and it is the grouping by minutes page that is correct.

The only way that I can see that would make this behaviour ‘make sense’ would be to assume that the ‘Total number of referrals with scheduled repayments for the next 90 days’ graph lists the ‘scheduled repayments’ as being due 24hours before they actually expire. I believe that this is a rather unclear/’ropey’ explanation however.

Link: http://www.neobux.com/forum/?frmid=8&tpcid=110291&msgid=1239514#m1239514

(more…)

SCREENSHOTS

Click on the images to view a larger version

SCRIPT DATA:

Script name: Neobux 2+ (v3)
Description: This script provides detailed statistics for your Neobux account and referrals (eg: ages of referrals, recent income/outcome averages, plus more!)
Version: 3.2.100228.1431
UpdateNote: 3.2 = Currently in the experimental development stage, adding support for chrome; 100301.1850 = BUGFIX: Fixed the R.Average in the stats sidebar - previously was not dividing by the time period thus was 7x too large (default);
License: WTFPL v2 - Do What You Want To Public License v2;http://sam.zoy.org/wtfpl/
License Summary: "Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed **as long as the name is changed** [emphasis mine]".
Time last updated: Sun, 28 Feb 2010 17:17:20 +0000

(more…)