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.
They should pay you monthly for your costs. (:
My work takes 40 gig and I can still play Factorio while working :)
Most cultures frown uppn it but cousin marriage is very common is some parts of the world. There is a great wikipedia article on Incest.
But I was really talking about the former. The likelihood that not a single crossing has happened since the beginning of like is very small.
I'm pretty sure all bloodlines have circles.
Ohhhh I thought it was a baby bird (little wings sticking out) with one weird eye and one winking eye.
Sex is very normal though. Just to make an argument here: what if sex had been banned altogether in the media when you were an impressionable child. How would that have worked out for you?
My guess is not better.
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.
They do claim to not share any medical data with third parties though. See other comments for source.
I wouldn't trust them either way...