Yep. I've been able to use the "wrong" (but still valid) expiration date on my AmEx for a long time. I've had other credit cards where the autopay info was never updated and it just kept working for at least 6 months.
Account Updater functionality isn't necessarily even involved there. In the end whether to accept a transaction is up to the issuer, and quite often they'll keep accepting recurring transactions on otherwise outdated card information.
Funny, the Amex on my Pixel Watch stopped working only a couple weeks after the physical card expiry.
It was quite confusing, because a) I received a replacement physical card several months before the card expiry, so by the time my watch stopped working I'd entirely forgotten about it, b) there's no indication anywhere in the Android/Wear OS of what the expiry date is or that it might be expired and c) there's no indication at the point of sale that the virtual card is expired, simply a generic "Declined" message.
You can run a charge with only the card number if you have sufficient trust. Each additional piece you add reduces liability and transaction fees (add exp, add cvc, add 3ds, ...)
We had an interesting architecture situation at work. Puppet Enterprise uses a single Postgres server. The company had moved from a recommendation of using a single PuppetDB API node (which fell over at high load) to running a PuppetDB API server on each compiler node.
That, however, came with its own set of problems. Of course you have to tune for concurrent connections as you scale wider, but there were much more serious contention issues than you'd expect, and the compilation times were terrible too. It turned out to be because those transactions locked the DB during their (synchronous) operations, and we had a globally distributed set of compilers in order to serve globally distributed traffic.
The solution ended up being to run a separate cluster of API servers in the same region as the DB. The expensive calls from the compilers to the API servers were largely async https so they didn't have to wait on the API nodes, and the API nodes could talk to the DB synchronously with low latency.
I'm surprised they got a reliable 10Gbps USB adapter. I've tried 3 of them and they're all trash. They cannot sustain multi-gigabit speeds and end up doing like 400Mbps when you hit them hard. I think I have sabrent and ugreen and one other.
They all just sit in a drawer, if I need a USB-C ethernet adapter i just grab my trusty 1 gig one.
Yeah, my home is cat5e (I think!) and I was only able to get 2.5 or 5Gbps to my _single_ 10GbE capable machine I had at the time.
So I ended up just buying a switch that supports 2.5Gbps over copper since it's such a huge expense to step up. Anyway, my devices are pretty much 2.5Gbps (APs, flex mini switches, etc).
Yeah, 10GbE-over-copper switches are SO expensive. I bought a Ubiquiti enterprise switch for my home; 10Gb uplink and the copper ports are split between 2.5G and 1G. It's fine because only 1 or 2 clients can even talk 10G, and those are all across the house on Cat5 links anyway so they only negotiate to 2.5 even on a 10G port.
As much as I wanted to "future proof" by having a 24 port 10GbE switch... why? I'll just wait and buy one when I have a use for it.
> As much as I wanted to "future proof" by having a 24 port 10GbE switch... why? I'll just wait and buy one when I have a use for it.
As much as I enjoy looking at those wiring cabinets where every cable is cut to exactly the right length to reach a single port on the switch, this is why I prefer to leave an amount of slack in the wiring: It's good to be able to pull different wires to different switches depending on your needs.
One small high speed switch with enough ports for the couple of devices that can use it. One gigabit switch with a lot of ports to provide connectivity everywhere else.
This is what I ended up doing. A 2.5G switch for the few devices that can use it and a 1Gbit+PoE switch for all the other PoE and 1Gbit and less devices.
It does, actually. I dismissed it originally because I don't need most of the capacity, but considering I have no 10GbE copper ports available, and my home is being remodeled and I'm running some new ethernet to the other side of the house, I could take advantage of these ports now.
Also, I didn't realize my UDM Pro was kneecapped at 3-4Gbps IDS/IPS throughput. I think when I bought it I only had a 1 gig internet connection so it was overkill, but now I've got 10gig. It didn't even cross my mind that I had this bottleneck.
Right, but for example my fiber ONT only has an rj45 port so I'm stuck using one of these for the link to my UDM Pro. The router and my core switch use cheap DACs.
reply