Transport for London does the same. If you add your (real, CPAN) card number to the "Contactless and Oyster" web service, it will also add all of the DPANs you have tapped in with on their network as separate cards.
That looks nice. I wrote a Swift book last year and I had originally intended on including a server side example but didn’t get to it. Hopefully I will add an example in the next edition.
I have preferred Lisp languages for the last 40 years, but there is something about Swift I like, probably the availability of great libraries like CoreML and good REPL support.
I recently discovered PocketSmith[0] which is not free nor open-source, but I have found it to be the easiest to keep up to date. It automatically pulls transactions from most banks and credit providers, which I've been unable to replicate with other solutions.
Yeah I use them too. I keep meaning to set up Firefly III to try it but Pocketsmith _has_ been really good. For a period of time I had accounts in a couple of countries and it was one of the few tools which let me get a multi-currency view of all my finances across the globe. Highly recommend.
+1 on the Pocketsmith recommendation. I've tried several others (YNAB, Lunchmoney, etc.) and I've been using Pocketsmith consistently over the past three years. It has integrations with just about anything, has support for crypto, etc. and their support is top notch.
I wish this site was more clear about which banks exactly are supported by bank feeds. It seems right now like I have to buy the service before I know if I can even use the bank feeds feature.
To more accurately forecast a balance, why not just enter transactions with future dates and estimated amounts? Then a balance report with the same future date will be a good forecast.
A nice write-up, however it looks to me that the Compute@Edge tests were being run on a free tier service (adding a credit card to Fastly account does not upgrade your service automatically, I know because I work at Fastly).
I'd love to see results from the same tests run on the full version of the platform.
Forgive me if I'm misunderstanding, but this looks like an end-user authentication system that you would implement in your own app rather than a corporate directory like Okta. Different use cases.
Yes, maintainability, ease of porting code, and ease of hiring knowledgeable workers do matter, and so does performance.
I hope Fastly stops calling things "cold starts" that aren't [1].
And, I think Cloudflare could do a quick find-and-replace on that article [2] to change "Fastly’s Compute@Edge" to "Fastly’s JavaScript on Compute@Edge". A phone call between friendly CEOs probably would have sufficed for that.
We all want to be on the same page when making these comparisons. Some may choose Fastly and write in Rust, some will choose Cloudflare and write in JavaScript.
