Should you wonder about the number of apps available in the #IzzyOnDroid repo slightly decreasing with the next sync: your gardeners were quite active again. Find details at codeberg.org/IzzyOnDroid/Every… – and be welcome to join the Cinderella, there are still many items left on the list!
Some other good news: after 6 years, Metrodroid (the app to read public transport NFC smartcards) finally received another update, which will go live here with the next sync around 7 pm UTC.
metadata reorg subtask: deciding about miscellaneous dormant apps
This is a spin-off from #10 where I'd like some input from the team, concerning how to handle the following unmaintained apps: * [x] [`ahmaabdo.readify.rss`](https://apt.izzysoft.de/packages/ahmaabdo.readify.Codeberg.org
Markus Henn
in reply to IzzyOnDroid ✅ • • •Is there an easy way for a user of a removed app to find out about that fact and the reason for the removal?
I might be sitting on a number of abandoned apps without knowing.
IzzyOnDroid ✅
in reply to Markus Henn • • •Markus Henn
in reply to IzzyOnDroid ✅ • • •IzzyOnDroid ✅
in reply to Markus Henn • • •@voks Be welcome to write one then 😉 You could diff the indexes for that. Hint: both, IzzyOnDroid as well as F-Droid use a binary transparency log such an app could parse for this.
You could of course also open issues at the fdroid clients' repos, to include such a functionality. Clients know what apps you've installed from which repo, and could watch for such removals when pulling index updates. That would be the best place to address this.