Northern started issuing them instead of cardboard tickets a few years ago and other TOCs followed along after Network Rail/Cubic finished adding barcode readers to ~all ticket barriers.
I understand why: paper barcode-only tickets are significantly cheaper than cardboard tickets (their lack of a magstripe allows any generic thermal printer to be used), but their larger form factor makes them a definite UX downgrade.
I think what you're describing is what the RSGB have been attempting to mitigate through the Beyond Exams schemes, wherein they've gamified different activities you could do on your own or with a club to further your knowledge of amateur radio. https://rsgb.org/main/beyond-exams-building-experience/
I think this is less of a big deal in London because-- and the article entirely glosses over this prospect-- TfL accept contactless (e.g. contactless-enabled debit/credit cards, Apple Pay, Google Pay, Samsung Pay). This means anyone can land in London and immediately ride public transit using their existing bank card.
Judo Payments | Angel, London, United Kingdom | Full-time
Judo makes buying the things we want faster, simpler and more secure. As Europe’s leading secure in app and mobile first payments platform, we’re riding an unstoppable wave as smartphones change the way we engage in commerce.
We sit at the intersection of mobile, SaaS and payments, three of the fastest growing and most interesting sectors of the global economy. Our customers - big brands and innovative Startups - win awards because of our outstanding people.
Founded by serial financial technology entrepreneurs in 2012, Judo is backed by leading VC and hedge fund investors.
We're looking for:
- DevOps
Help design, build and maintain our IT infrastructure to meet our growing needs. Monitor and maintain our production platform keeping all components in top working order. Automate all the things; help us scale quickly by automating all the daily chores leaving you to focus on infrastructure improvements. Strong Microsoft Active Directory knowledge, including associated functions such as Group Policy, DNS etc. Experience of Microsoft Windows Server 2008 / 2012 & Linux. High level of automation using Octopus/ssh/powershell/bash. Experience of Docker. Experience of PCI.
- Postgres DBA Developer
Experience of working on very high transactional load in always on mode. Experience with highly volatile load profiles. At least 2-4 years of administering large PostgreSQL databases. Experience in performance tuning / index maintenance, able to meet and assist the needs of the Development teams using PostgreSQL as its backend database. Designing and Managing PostgreSQL database schemas. Experience in Security access control. Experience with version control. Experience with 24x7 zero downtime database management. Experience with Java and high-available web applications. Knowledge of fault detection and resolution processes. Ability to communicate effectively to different levels of technical and non-technical audiences. Implement Database Change Controls. Experience supporting BI internally and for customers. Experience of, or willing to learn alternative database technologies (NoSQL) such as Mongo, Redis, Cassandra.
Our stack is based on C#/ASP.NET MVC, jQuery/Angular, RabbitMQ, and MS SQL Server/PostgreSQL.
If you're interested, please email [email protected] for more details.
No. Creating the customer will charge the card $0.00 or $1.00 (depends on country/bank) and immediately refund the charge to verify the card itself, the CVC, the address, etc. In most cases, this tiny charge won't be noticed because of the refund.
If you attach the card to a customer object[0], you can create one off charges whenever you'd like. Stripe will even update the card's details on the customer if the card is reissued[1]. You can then create charges against the card manually through the dashboard (which seems to be what you were looking for based off of your original comment).
You are allowed to keep your FERPA recommendation rights but, as misingnoglic, most universities will not pay much attention to your recommendations if you choose to do so.
I wasn't aware of Wells Fargo issuing Chip and PIN cards[0] and I appreciate you pointing that out!
The other USA banks that I've looked at (Bank of America[1], for example) issue signature-only cards. These not working in unattended kiosks is mentioned in the last paragraph of the Wikipedia section we're both referring to.
The main problem with Chip and PIN cards in the USA is PIN management. Since EMV was developed before every ATM was online, the card needs to be aware of its PIN. Not many USA ATMs support reading EMV cards, which makes changing the PIN on the card difficult.
This is why Wells Fargo[0] don't allow you to change your card's PIN and is why many USA banks simply chose to skip PINs altogether. The last sentence of the Wikipedia section we're referring to mentions this.
Square Wallet[0] used to implement something similar to what you're describing. It used your phone's GPS to register you as near/inside a store and merchants selected you based on a photo you provided. It was pulled in May[1] in favour of Square Order.
As an aside, no USA banks issue chip and PIN cards. The EMV-capable cards being rolled out are chip and sign cards. This usually doesn't matter but can cause issues at fully automated tills (the common example being issues when trying to purchase transit tickets).
Wikipedia's article on EMV has a section explaining the technical differences[0] between the card types.
Each message is encrypted individually for each device that will be receiving the message. As a result, unless Apple slip a public key they have control over into the keys reported for the receiver, they cannot read your messages. (This is why abalone mentions that Apple do not have access to your old messages.)
> Digital Ocean, for example, won't give you more than 1 IPv4 address per VPS, which means you need a separate VPS for every side project, if you want to go HTTPS.
As long as you're not supporting clients running IE on WinXP or other similarly old web browsers, Server Name Indication (where the hostname is included as a part of the handshake) will work and it'll eliminate your need for more than one IP.
Wildcard certificates are only valid for the subdomain level directly under it. [1]
If I get a wildcard certificate for example.com (the common name is set to *.example.com), foo.bar.example.com will throw an error.
It's not. As https://developers.facebook.com/docs/chat/ explains, "Facebook Chat should be compatible with every XMPP client, but is not a full XMPP server. It should be thought of as a proxy into the world of Facebook Chat on www.facebook.com.
Take a look at me.com, for example. Before Apple bought it, it was owned by SnappVille.com. If SSL certificates didn't expire, SnappVille could have continued using their certificates for me.com.
Comcast still offers CableCARDs to new customers at least (https://www.xfinity.com/support/articles/about-cablecards)