Maintaining our own AppVerifier directory

jonah: > It’s been brought up that maybe we could simply release a fork with an expanded internal database too, I think a fork that you guys maintain, that we can contribute to would be a great idea. jonah: > but I am not sure because I would think people will want to obtain AppVerifier from Accrescent, and we couldn’t publish a fork there (at least not yet). This is long winded, but as I can’t read code. I typically download most apks from github and check their SHA256 code they provide, against the apk I have downloaded. Then check it against AppVerifier as well as uploading it to VirusTotal before I install. That’s just me, but I think if you released it on Github and listed the apks SHA256 for people to verify. I think people here trust you and your Team enough that might satisfy them.