Penalty for not tapping the Opal card is too high

I've been a bit ranty lately about Opal cards. Not working from within your wallet; the wait even at our small station, even when there are only a small percentage of travellers using it; how much it's going to cost me for forgetting to tap on where there is no gate to pass through.

This last point I guess I could chalk up to forgetfulness tax - perhaps it will even train me to remember. A small price to pay I guess, two dollars or so penalty to rewire my brain. Not so costly as to make me do the wrong thing and jump the gate when I realise that I forgot to tap on.

Today however, I realise* that it is a little more costly than I imagined:

Not only do you get charged for a full network journey, but it does not count your trip! Remember that the "weekly travel reward" fare discounting system on the Opal card is based on paying for only 8 trips per week. That means this trip that was charged full price, and not counted in fact cost me $5.67 extra. This changes things a little. I don't know that I will be as inclined to do the right thing at a cost of five dollars.

The whole idea of penalising people for forgetting to tap on or off is a bit wrong in itself if you ask me, but this almost seems like double dipping with the penalty - I mean I did take the trip, you charged me for it, count it. Can't we just presume that most people are honest and charge me for the journey that I usually take? We could do this at the station window if you like - might give the station attendant that used to sell tickets something to do in this new system... The trip at least should count.

Perhaps it is a bug in the system*. Perhaps it will be one that causes quite a bit of extra revenue** in the system: I wonder just how many people are forgetting to tap and as a result paying for 9 or even 10 trips in a week. I wonder would Sydney Trains be inclined to fix this kind of problem if it will be a cost in lost revenue for them to do so.

I wonder.

---

* Okay, so I did just check on the Opal default fare info page and yes it does mention this. But only mention mind you, I think they should probably point it out more explicitly just how much it will cost you to not tap on or off. And I still think it is too great a penalty, until they have gates at all stations and the only way to "forget" is to "accidentally" jump the gate.

** So not a bug, but I would like to know what percentage of the revenue is trips that are accounted as "No tap to/from xxx"

correct horse battery staple

I have been bad. I have re-used passwords. Mea culpa. Sure I have lastpass and generate great, strong, long passwords for most sites, but what about apple id that I have to type in on the phone, or live.com that I have to type in now to log into my windows 8.1 instance? It is just too hard to remember good secure passwords. Or is it...

xkcd password generator

I have pretty much switched over to using passwords/passphrases of this type when I am likely to have to type the password in, or tell it to someone else (live.com does not do shared developer accounts, I have to give the marketing guy my password so he can update the app description... but that is a whole nother rant) I just change over to it, still store it in lastpass and have to look it up maybe a few times but after a week it is stuck in my brain, and it stays in lastpass should I ever forget it. These longer passphrases are pretty much immune to shoulder snooping too, just too many characters to follow as long as you are not holding the device perfectly still.

So I was just resetting the password on live.com as I was sick of trying to type in g2A16S0DDFt4efsv just to log in, and generated up something like "look double headed parts". But am foiled thrice by Microsoft's take on what is a secure password:

"Your password can't be longer than 16 characters."

Geez, really? You can't spare a couple of bytes? Okay then, this is less secure... it's not my personal account so - care factor - m'okay: "look double part":

"The password contains characters that aren't allowed."

Wha? Is it the spaces?... It's the spaces. FFS are you serious? "lookdoubleparts"

"Please choose a password with a mix of lower and upper case letters, numbers and symbols."

Well, okay that is probably a reasonable objection, so what do I end up with now? "l00kDoubleParts"

Wow. So easy to remember (see xkcd).

So your advice Microsoft is this: "Make a password with different cases and symbols, wait, wait, not that symbol, good, good, hey no, not so many." Strangely enough, it will accept "password1" which should pretty much be universally banned.