@organicmaps Great! Please do not forget to update the link on your website 😉 And to let @fdroidorg know they have to update their recipe 😜 I've just done it at #IzzyOnDroid – and promptly an update was fetched which, according to the tag date, was waiting there for a couple of days already 😉
PS: RiMusic sends a warning, please read for yourself. One of their (now former) collaborators went rogue, so they ask you to NOT use their (former) Discord – and also be careful with the fake RiMusic app that showed up at PlayStore. RiMusic at IzzyOnDroid should still be safe.
🇬🇧 After running #IzzyOnDroid on my own for over 10 years, we became a small team over a year ago. All done in our spare time, no grants.
That finally changed this week.
We're excited that we're one of seven projects being accepted for the NGI #Mobifree grant! 🥳
Finally we will be able to focus on some more things on our wish list that we've wanted to do for the community for a long time. Stay tuned, we'll update you with details later!
@aral Ever seen the HTML produced by an MS Word export? Blood fountains from your eyes. I once cleaned up such a HTML, and the size of the resulting clean HTML was less than 20% of the original. They even used CSS classes, but then explicitly repeated their definitions every.single.time (like "<p class="foo"><font size…><font family…><b><i>blabber</i></b></font></font></p>", with "foo" of course having font size, family, italics, bold already).
Das und mehr gibt es bei https://weingaertner-it.de/ – dort kannst Du auch PeerTube, Friendica und mehr hosten lassen, ab ca. 6 Euro im Monat. Der Betreiber ist auch selbst hier: @weingaertner_it
It's repo had been archived half a year ago, and the last release was made almost 3 years ago – so it would be good to know if we should still keep it at #IzzyOnDroid or have to remove it as "no longer working".
@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: