I followed the compose file in the docs with podman and it was fine, configured headplane as the management gui inside the same compose. I then later converted the compose to a quadlet and it continues to be fine. I leave it alone, it leaves me alone

I think this lets you host that management connection yourself.

No, but if you wanted to do that, headscale is the answer

yes that is the cynical take, and I mostly agree, but installed apks list their install source, so if that information is there, then its simple to give the user the ability to mark said source as trusted. But to do this under the guise of security, when there is more malware on play than fdroid is such a head scratcher

I just want to know what is going to my fdroid apps when this comes in. Will they all get binned? Disabled? Just fail to load until I jump through the new “untrusted” sources hoops?

What gets me is that upstream linux has had this solved by trusting repo keys for years, why not let the end user be the trust arbiter