Thanks! I will pass it along and hopefully we can push for a change. I can’t guarantee that anything will happen in the short term, but at the very least we can create some bad publicity for them.

Hey Op, since you appear to be somewhere in the EU based on your mention of Euro pricing, would you be willing to name and shame the wheelchair manufacturer and/or model?

Without giving too much of my own personal information away, I might be in a position to cause a bit of ruckus for this particular company in terms of bad PR, possibly legislatively. I work for a company that profiles itself on doing this stuff “the right way” (secure practises, not screwing users this way, etc) and we are working on building a list of practises we are hoping to root out EU-Wide with some examples that are clearly exploitative.

I need nothing personally identifiable, just the brand and model, and I can pass it along to the team that can investigate further.

Tell me you’ve never used PHP without telling me you’ve never used PHP.

It’s known for giving a complete stack trace, it’s nearest neighbours and their god damn grandkids the moment it so much as coughs up a warning. For the longest time it was notorious for doing this as the default error logging level.

I’m aware it’s cool to hate on PHP, but it has plenty of things to dislike without straight-up inventing nonsense.

My tried-and-tested method has saved my (company’s clients) ass a few times.

Every Mysql/MariaDB server has at least one replication target. This replicant is not used for access by the infra, and can be paused, restarted, etc with no issue and is configured with this in mind.

We run a mysqldump on the replicant. Depending on the resiliency required, we store the dump on the replicant and/or a third location.

The tools differ, but the practice applies to pretty much every database system and the database has the benefit of not being interrupted during the backup (replication is paused during the backup, and resumed after completion). This also has the benefit of already having replication configured, and adding a secondary redundant instance you can swap out for the master (or using the backup replicant in a pinch) means disaster recovery is much faster.

Also, I dislike many things about Azure’s offerings, but their Flexible Database for MySQL does the above for you as one nicely packaged solution for a reasonable-but-not-cheap price.

Yup. Okay-ish solo, but amazing with a friend or two.