• 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: September 26th, 2023

help-circle




  • It’s already trivial to get local banking details from many countries, (e.g., ‘multi-currency’ debit cards) but as far as I’m aware there’s not a practical way to get a foreign debit card without the usual hoops that the full account would require.

    Probably because demand for such a thing is low - I can generate disposable card numbers on the fly, but only from my home country. Can’t imagine (aside from this specific edge case in question) generating foreign card numbers would be all that useful most of the time.

    End-user support for such a thing would also be a challenge - I’m very accustomed to entering the usual data points with my card, but users would forget the associated postal code, or any number of other things, and then call support whining that it’s ‘broken’.





  • In green fields projects, this makes a fair bit of sense at initial reading, tentatively.

    But new code becomes old code, and then builds on the quality / discipline / cowboy status of the last person to touch the code, in a complex and interlocking way.

    I can’t say I’d be excited to find a partially converted existing codebase of this. But in fairness, I’m on my couch on a Sunday and haven’t actually worked through your examples (or read the original paper). I see the benefit to having both types of extensibility, obviously. Just not sure it outweighs the real world risk once actual humans start getting involved.

    I don’t know a single person who can’t say they’ve never taken a single “good enough” shortcut at work, ever, and it seems this only works (efficiently) if it’s properly and fully implemented.





  • Right there with you on “just works,” as well as the simple fact that the config snippets you need are readily available - either in the repo of whatever you’re putting behind the proxy, or elsewhere on the internet.

    I consistently keep in mind that it’s ultimately an RU product, of course. But since it’s open source and changes relatively infrequently, that’s mitigated to a large degree from where I sit.

    Nothing against Caddy, though Apache gets heavy quickly from a maintenance standpoint, IMHO. But nginx has been my go to for many, many years per the above. It drops into oddball environments without having to rip and tear existing systems out by the roots, and it doesn’t care what’s behind it.

    Ages ago, I had a Tomcat app that happened to be supported indirectly by an embedded Jetty (?) app that didn’t properly support SSL certs in a sane way on its own.

    That was just fine to nginx and certbot, the little-but-important Jetty app just lived off to the side and functionally didn’t matter because with nginx and certbot, nothing else gave a crap - including the browser clients and the arcane build system that depended on that random Jetty app.