@dansup@loops looking forward to see you here! Read about loops a few weeks ago and was hoping for something like that, so I'm excited, too! 🤞 the APK will not be too big 🙈
@dansup feel free to ping me from the issue then should you create one, I can e.g. give you the full scan results there and maybe help finding "partial solutions". With the "library problem" solved, maybe I could also make an exception size-wise. We'll see. @derfopps
@dansup Das ist leider mehr als das doppelte des per-App Limits bei IoD. OK, ist ja ein "Fat Build" (mit mehreren ABIs) – mit per-ABI Builds ließe sich da noch etwas machen (native libs sind unkomprimiert, jeweils 8 MB – also single-ABI wären die APKs ca. 50 MB; immer noch zu groß) Oof, und der Sacnner findet 7 "offending libs". MLKit ist Schuld, zieht Firebase+GMS mit rein.
Hast Du ein Issue dafür? Dann kann ich mal schauen, ob ich helfen kann. MLKit wird aber schwierig…
@starlabssystems I must say seeing how you handled this makes me remember your name. Kudos! Should I ever need a device like this, I'll surely remember were to look first. Thanks for caring*!
*Unfortunately not a given these days, so happy seing your light shine bright there. @aral
Also weil Betreiber es falsch umsetzen, verzichtet man lieber ganz darauf - und hofft auf freiwillige Transparenz? Wow. Wieviel hat die Lobby dafür gezahlt? 🤦♂️
@aral@opensourcedesign@simulo@fosdem If that's Google's belief – then why are so many of its core services proprietary, and why did they replace one AOSP app after the other with their own proprietary counterparts? 🤔
"The actual risk scenario would be that a github repo owner build an APK from sources other than those on the repo and upload it to the repo"
That indeed is a real risk as I have no means to check that. There are other checks in place (library scanner, VT etc) which should reduce the risk of "bad stuff" – but a little risk always exists. So you need to trust the developer, too…
@aaribaud No. As the "Readme's" say, my repo serves the APKs built by the developers. Just follow the "details" link at the top of the list 😉 Or go directly to the question you raised via this link:
@aaribaud Well, their APK is close to 0 MB. My repo runs on my personal space and thus has a size limit: 30 MB per app. Which means, their mail app simply does not fit in, or it would be there 🤷♂️
@ilumium How fitting: the @EU_Commission uses SurveilanceAds to promote its planned surveillance tool. This makes it even clearer what the real purpose of ChatControl is – and that the official arguments are nothing but "wrapping it to make it look nice". Despicable.
Ylva should have her chats controlled – and then step down. I don't see how else the commission can be salvaged; this shows the commission as it is now cannot be trusted.
(I'm currently adding "AntiFeature reasons" to F-Droid apps having AntiFeatures such as NonFreeNet to make clear why. Currently running: Batch 19. Next build cycle will lift the latest F-Droid client to "recommended"; that one is already available and able to display those reasons. I'd say "try it out", but it's Android and you're on iOS 😉)
What a day! Two more apps got all their AntiFeatures stripped and are libre now. For one of them that means not only the return to my repo at a quarter of its size (85 MB => 24 MB for the "fat APK" with all ABIs), but also (spoiler) its going for the next goal and entering F-Droid soon™. Stay tuned!