I have fond memories of Flash 5 in early 2000s. At the time I knew BASIC and Pascal. I could figure out how to draw things, how to animate them using keyframes and motion tweening, and how to make things interactive with ActionScript, all by poking around and reading the help manual (F1) on our underpowered offline PC.
I've realized this as well, the bigger the company the worse the experience.
The more customers they have the less they care about any individual customer.
The more products they have the less they care about any single product.
The more employees they have the less they care about each individual employee doing a good job. And there's no they any more, there's a big, soul-less profit glutton.
I was investigating this 5 months ago and the answer their slop machine gave was:
> Does Mollie retry failed payments (dunning) and track subscription states?
Mollie does not currently provide automatic dunning or retry logic for failed subscription payments. Subscription states like active or past due are tracked, but you need to implement retry and notification logic in your system. This is a common feature request and may be on the roadmap, but no official release date is available.
From your link, note though:
> If your subscription payment does not succeed, Mollie may attempt it again up to 5 times (once a day), depending on the failure reason. After all retries have been exhausted, the subscription will be cancelled.
If there's a payment issue, I would not consider cancelling the subscription 5 days after the first failure as reasonable. I would expect the subscription to go into "past due" state, and to keep retrying.
Do you know of any EU payment processor that supports recurring payments like a SaaS would need (subscriptions, subscription state tracking, automatic retries of failed payments)?
I looked but couldn't find any. Adyen does not do this on its own AFAICT, only with 3rd party addons that implement recurring payments on top of it. Mollie claims it does this but is woefully incomplete (no failed payment retries for example), and appears to be all in on slop.
I hope that changes and people start valuing simplicity and robustness over electric gimmicks (I know many people already do, but we need critical mass).
This is open source, volunteer developers often focus on doing things that are fun to them, or that scratch their own itch. I can't imagine dealing with Google Photos semi-broken exports is fun to anybody, and you only deal with the pain of the import once, afterwards there's no itch to scratch.
It would be interesting to see vanilla postgres on a VPS and vanilla postgres on a bare metal server included too. I understand it's apples and oranges, but would it be slower, would it be faster, by how much?
I add a note in the password manager's notes field for sites where I've added Yubikeys as the second factor. I can get the list of the sites using search, and from time to time I go through them to check if a backup key needs to be registered. I create new accounts infrequently.
A little nice thing the cars could do is automatically calibrate the speedometer from GPS when on a long stretch of a road. You would get the accuracy of GPS and the reliability of speedometer even when in city jungle, underground, during slow speed manoeuvres etc.
[email protected]