@resist1984
Quite right, we've improved our organisational skills in a number of small ways but that is an area we've not considered.

Fedilab have a notes section. These days though we're cautious about mentioning Fedilab, dev appears to be taken over by interests that feel its more important to lock out #Android4p0 to 4.4 users with smaller devices.

There's even a danger #FDroid will drop older phones. Once that happens we'll be pushing #APAB (#AllPhonesAreBad).
@selea

Its not just that they are smaller though, they have removeable battery etc.

As you may already know, we produced (#)FediFlyers that anyone can print. They contain multiple variants and one allows you to operate a private local #BugBounty program for Fedilab. And other Fedi softwares.

We just feel the more eyeballs that we can get on the code the better.

Sorry for the long discussion, @selea. Do tell if you're less interested and we can not include you, if we continue.

@resist1984

@dsfgs @selea i noticed you're using a dvorak keyboard (from your typo). That's often hard to pull off because so often the J & F keys are made with a unique socket that makes them hard to rearrange. But yeah, i'm with you on the forced chronic upgrading that Android apps often impose & even though fdroid apps tend to be higher quality, respect for compatibility tends to be an exception.

@selea @dsfgs if the #fdroid app itself starts disrespecting old phones, at least side-loading is still an option. But it's a shame that even FOSS projects are chasing the shiny at the cost of the environment.

@resist1984
AFAWK, right now it is just something that FDroid were floating. There is no timeline, so hopefully its not something they persue.

We'd much rather instructions on the front page of their website, "Have an older phone? Here is a step-by-step guide to updating your CA keys."

We realise its a tricky situation that people with older phones are faced with, but software updates shouldn't dismiss good hardware.
@selea