My banking apps work fine on Calyx.
Banking apps normally check for rooted phones as the thing they don’t like. Because pixels come with an unlocked bootloader, you don’t need to root the phone to install a custom ROM, and so banking apps are still okay.
Haha yeah, fair enough. Applogies for turning your deserved whinge into a serious question.
Wrangling annoying customers is always the most annoying part of the job isn’t it. How nice it would be to spend more time programming…
Technical requirements are often ambiguous when written as free text, the way someone would speak them, because as you have discovered the free text fails to capture where the linguistic stress would be that disambiguates in speech.
Instead, I suggest using a format that is more suited to text.
I would recommend a table. Email the customer back with your current interpretation of the requirements, with a column for outcome and a column for value. Ask them to check and sign off on the table, or to correct the table where it is wrong.
Example:
| Outcome | Value |
|---|---|
| NULL | x |
| Complete | x |
| Cancelled | x |
| (Other) | x |
There are edge-cases with if outcome can be "Complete or Cncelled
Seriously. Saw that in the cinema and couldn’t hear a word.
In part due to this, it has also become trendy and normalised to have bassy dialogue and lots of environmental noise, because that’s the expected “epic movie” feel.
So it’s almost become a self-fulfilling prophecy that movies will sound this way, regardless of the anticipated audio hardware.
Yes, it absolutely is automated.
There are bots running constantly looking for things that match patterns for exploitable credentials in public commits.
AWS credentials
SSH keys
Crypto wallets
Bank card info
If you push secrets to a public github repo, they will be exploited almost immediately.
That Cloudflare were justifiably unhappy with the situation and wanted to take action is fine.
What’s not fine is how they approached that problem.
In my opinion, the right thing for Cloudflare to do would have been to have an open and honest conversation and set clear expectations and dates.
Example:
"We have recently conducted a review of your account and found your usage pattern far exceeds the expected levels for your plan. This usage is not sustainable for us, and to continue to provide you with service we must move you to plan x at a cost of y.
If no agreement is reached by [date x] your service will be suspended on [date y]."
Clear deadlines and clear expectations. Doesn’t that sound a lot better than giving someone the run-around, and then childishly pulling the plug when a competitor’s name is mentioned?
Yes