So... there's a bit of a correlation, eh? Could be that voters come in during the jam, and only vote on what they see and never come back, OR it could be that the earlier submissions have had time to polish and are completely done in good time and thus are more likely to get votes
Well I've got a rough prototype of custom game jam software that lost interest after I went on vacation this April.... I'm very willing to develop this if an individual or small committee would like to provide requirements that I can work closely with - gamejammed.com/GDSESpring2014
In early October Apple turned on Apple Pay, which is an NFC-based mobile payment system that works with it's TouchID stuff and focuses on convenience and privacy (in the sense that merchants who process the transactions with Apple Pay do not get to see anything about you -- not your name, your card numbers, etc; just an anonymous token).
For the last few years a conglomerate of retailers called the Merchant's Customer Exchange have been working on an alternative mobile payment processing system called CurrentC.
CurrentC's main point is avoiding credit cards, so merchant's do not have to eat the credit card swipe fees. It's also focused on gathering customer information, and using it to feed into loyalty card programs and so on.
A few weeks after Apple Pay went live, a few retailers disabled their NFC terminals -- effectively turning off both Apple Pay and Google Wallet.
Turns out these retailers are MCX retailers, and are presumably doing this because they are contractually obligated (although that's been denied by MCX now) or are just trying to discourage adoption of Apple Pay in the hope that when CurrentC starts to roll out next summer that people will prefer it.
A lot of people -- particularly pro-Apple folks -- have tried to spin this thing as a "MCX-versus-Apple" thing, which is maybe sort of kind of realistic.
But mostly CurrentC is a horrible, horrible system irrespective of Apple and Apple Pay.
It's massively clunky, using QR codes and mobile apps and token-based handshakes, it requires a massive investment of your personal data (social security number, bank account numbers), and it works as a debit system and not a credit system (obviously, to avoid CC swipe fees), which means it's probably got much, much weaker fraud protection than credit cards do.
And they've already been compromised. There was an interesting article on iMore about the data they potentially collection and/or will send back to you in the clear.
@SethBattin And to be clear, CurrentC doesn't avoid fees for the customer, only the merchant. There's basically no benefit to the customer in this system at all, unless you really really like loyalty cards.
(which themselves mainly exist for merchants to data mine your soul)
i am current parsing XML that is sent with a wrong encoding written at the top of it in order to extract a single continuous string of error messages from one node which was generated by serializing a stack trace from a caught exception, in order to determine why a "RESTful" service which transmits all its data in post-body-XML failed