You are absolutely right. It was inline comments I had in mind.
You are absolutely right. It was inline comments I had in mind.
Absolutely, although I see that as part of why
Why is there a horrible hack here? Because stupid reason…
Comments should explain “why”, the code already explains “what”.
You cannot seed files that are altered. It’s not the same files anymore.
So yes, as long as you want to continue sending, you need to keep the original files around.
The package name is the unique id. If you want to distribute multiple variants (like two versions with differing signatures) they should not have the same identifier. If they are not the same the id/package name should not be the same.
Having different package names would also prevent the Google play store from trying to update it.
It’s a problem of trust. Differing signature is an indication of third party tampering. People shouldn’t start to see difference in signatures as an ordinary occurrence. It should be an high alert event.
Mismatched signatures have been discouraged since day one of Android. A mismatched signature is a sign that some one other than the original publisher built this package, and the user needs to be aware that it might be malicious.
That F-Droid went with this setup with mismatched signatures was always going to make their apks look suspicious.
This is an f-droid problem. If they use the same package name, they need to use the same signature. That has been the case since long before f-droid existed.
They could just build apks with alternate package names and this wouldn’t be an issue.
I imported (to Sweden) a G1 from Germany in 2008. A bunch of experimentation on that and my next Android phone the HTC Desire Z in 2010 eventually helped me land a job as an Android developer.
15 years later I’m kind of sad about where it’s all headed. Surveillance and user lock in…
That is stupid. Those commands are for different use cases.
If you know how the code does something, you also know what it does.