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…

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. (:

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.

Because that is the only valid date format, ever, everywhere. There are just too many of them in this graph.

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.

Might be because I’ve been reporting all sponsored content as spam.

It’s even worse when you can tell they really tried and still end up with spaghetti. Even mid- to senior developers do this. Rhe more senior they claim to be are, the more embarrasing when you have to get the stick.

Some people try to be so clever with fancy design patterns or bit-tricks, instead of just solving the problem, you now have two problems and a solution to one of them.

I have an alias that tries both names

Redis, rabbitmq. There are infrastructure where all nodes work but only one node is responsible for properly and timely synchronizing changes, which is a hard problem to solve in a distributed fashion.

Yes, both of those may already be servers

Interesting typo. Almost like a Freudian slip but with melting batteries instead.

It has similarities though, as pointed out in orher comments. For one, a user might be more careful with downvotes if they are afraid of negative consequences e.g. harassment. With piblic votes, there would therefore be a bias towards upvotes and and people abstaining from downvotes, i.e. less interaction in total.

Downvotes serve a purpose today, letting us quickly scan which comments are controversial or even harmful to the conversation. I, for one, usually sort most threads by votes and then skip the comments with many downvotes but for controversial topics, I instead seek out the comments that have both many upvotes and downvotes.

These would be harder to find given the above bias.

Yes but I find all this both racist and sexist. Not all men in India are creeps, even if may be a rampant problem. Shouldn’t they instead try to punish the weirdos?

How about “we let private companies segregate in whichever ways they want!”?

Forcing Russia to defend so they can’t be on the offense any more.