install update

Elliptical curve for RSA was immediately phased out

what? when did RSA want to use elliptical curves? its a completely different technology. and ECC itself was not phased out of anywhere. certain curves were, not ECC as a whole.

And if I remember correctly, I believe it has more weaknesses (especially potential unknown ones) than RSA.

what are those weaknesses? so far I have only read for users that ECC is more secure than RSA

But it’s definitely more efficient on embedded hardware,

not only on embedded hardware, but everywhere and also in network transfer because of the smaller keys

it wasn’t really a clusterfuck, but whatever. yeah, sure it didn’t have rounded corners and large empty spaces, if that’s what you mean

also, what do you do with the leaked keyboxes? does kernelsu handle them too, or do you use a different tool for that?

https://github.com/tiann/KernelSU

To help translate KernelSU, we no longer accept translation contributions via Weblate. All translations are now handled using LLMs.

what???

I think you can get to it also by searching “f-droid” inside f-droid

what things you don’t like?

open the app’s page and expand versions. the last one was just not marked recommended yet, in case there are serious bugs

I’m always ready for some ursula blaming but the first two are really not the fault of the law. majority of the companies “comply” maliciously, often also illegally, to make people hate privacy laws

it does not say part number is baked in. it says parameters are baked in (latencies, frequency), and so chips with a different part number might not work.

That’s neither the law nor the ethical requirement.

the law needs to be changed, and your lack of ethics is your subjective preference.

As a photographer I’m a firm believer in the right to take photos and videos in public, for both artistic and documentary purposes.

sure, no problem with that, just be careful.

There is no expectation of privacy when in a public place

that’s blatantly false. However much you deny it, there is an expectation of privacy in public. we are not going out to have a chance to be acting on your photos and videos. we are going out because we need to, to go to work, the shop or to the doctors.

it would be right to say, there is no expectation of being invisible, or that nobody will see me do my things on the street. and of course if we do something silly, people will see that and judge us. but that is not what you said. there is an expectation of not having a permanent record of our own lives if we don’t want, and anything standing in the way of that needs to go.

that being said, yes, you can take photos and videos in public. granted that there are no unconsenting people in the scene, or that they will not be recognizable in the resulting images. otherwise dont be surprised if you are being judged.
recognizability does not only mean, whether do I know that person, or whether the face is visible. photographers are notorious for uploading their images to tech companies that have the capabilities and the practice to do their magic on photos to recognize people by their other attributes.

likely not the reason. haven’t seen anyone denying the existence of AI so far. the other two user’s explanation sounds more plausible

waves, oww noo, shouldn’t have done that!!

Actually the problem is that they are too widespread. if something happened, and they started creating fake certificates, for outside force or otherwise, they can’t just be blocked because literally half of the internet or more breaks. what’s worse, if browser vendors trued that, people would be downgrading their browser to the last version accepting it, and become exposed to publicly revealed security vulnerabilities. not all because its a bit complicated, but enough would do to have it cause an even greater problem.

which is still there if you are not using lets encrypt, because they can strongarm them to make a fake cert for your domain, and install a proxy repackaging HTTPS traffic with the fake certificate. all browsers trust the lets encrypt root certificate, so they won’t see anything suspicious.

the only thing there today to detect this (but not avoid) is certificate transparency logs. all modern certificates are required to be added to this log, for the CA to remain compliant. but browsers are not checking the logs, that would be a lot of additional traffic and how do they decide if a certificate was created maliciously? also, lets encrypt could afford being noncompliant, browser vendors can’t realistically just distrust their root certificate, many sites would become inaccessible.