They should pay you monthly for your costs. (:
They should pay you monthly for your costs. (:
Not if you ask them but taking the time to design a system that isn’t reliant on a strong client (and then open sourcing it) would probably be more secure, and obviously more inclusive.
For instance, I’m very eager to switch to a lknux phone but having blockers like this is forcing me to stay on Android, even though I am sick and tired or the enshittification.
Or even run the app as is on a “non-compliant” os - like a rooted android.
What I meant was that the phone operating system has SDKs (e.g. google services on android) which the app uses to make sure it hasn’t been tampered with, which makes it even harder to make an open source client.
It’s the opposite of supplying an SDK for third party developers.
They are using the phone SDKs to verify that BankID was correctly installed, much like any other client side DRM.
I think you mean cue, not queue.
That’s not how pricing works. They already have the price they think makes them the most money. Raising prices means losing customers to competition, netting a loss.
So they would just lose 1000 customers and not raise the price because that would mean an even higher loss.
It’s different, of course when including that all ISPs would be hit with this. One can only speculate what will happen. All those pirates will want alternative ISPs, probably paying extra for privacy. The rest will stay in a dying market where competition for the remaining customers would be fierce, probably with lower prices.
Interesting typo. Almost like a Freudian slip but with melting batteries instead.
“Never install, carry or handle”. OK but what are they for then?
That’s the usual open source way. The config probably came later so they just added the option without changing the default because that would break backward compatibility.
And there would be too much boring work to build a migration.
I guess that wouldn’t help the deaf people though. (:
There were a few years when only a handful were supported. Before that it was as open as now, leaving compatibility responsibility to the extension developers.