This looks like an AI generated ad disguised as a discussion...

Best way is to not include it in the first place by using another ROM. If that's not an option, you can always remove it via root. It may also be possible to use ADB/Shizuku to get rid of it, but Google could add checks to prevent ADB from removing it. Then again apps installed via ADB aren't subject to verification.

I've been using a Vero V from the OSMC project. It runs Kodi and comes with a remote that's simple enough for my family to use. Kodi has been around for ages and is great for both local library content as well as add-on based content. The OS is based on Debian so you could run some other services on it. The SoC has support for AV1 hardware decoding (as well as all the older codecs) and can play 4K HDR10+ content to my TV without issues. There's also Dolby Vision support if your TV supports that. It's probably not the cheapest option but I wanted a small form factor and good UI that my family could use without having to be tech wizards.

Maybe it's the endpoint Syncthing uses for NAT traversal or fetching the relay list. Other than that I'm not sure but you could ask the developer, they respond to questions quickly.

I know I'm not directly answering your question but I switched from Catfriend's last build to BasicSync. Sure, it doesn't have the same bells and whistles as Syncthing Fork but importing worked fine and it's been rock solid since. If you've ever used the Syncthing web UI on desktop you'll be fine. Plus the developer is well known in the Android development circle.

This is it, what they've been wanting all along. You will no longer be able to access vast swathes of the internet unless you have a Google approved device, that is a Google-certified Android device with Google Play Services (aka Google Play Spyware) or an app on iOS. Use GrapheneOS or a Linux phone? No internet for you.

What I'd like to know is, what if you're already accessing a site from your phone? And what if you genuinely don't have another device? I'm assuming the answer to the second is you're SOL.

Finally, repository specific access tokens were added! I was missing this feature from GitHub (fine-grained access tokens) and had resorted to making service accounts that had access to a single repo. Time to clean that up :)

Perhaps try Authnkey which is more recently updated. If that doesn't work then some details like which security key you are using and over which protocol (USB or NFC) would be good to know.

Maybe people don't care but some do. I am sure I am not alone in caring. I believe every user should have the right to know what is running on their system and where it came from. What they choose to do with that information is up to them.

Sigh. I knew uv and ruff were too good to be true. Just hope the community can fork before it all goes to crap.

Ultimately that is your choice. I personally will not use researchxxl's version considering they appeared out of nowhere and there was 0 communication about the transition. For now I will continue to use Catfriend's version and perhaps switch to nel0x's in the future.

No, the maintainer of syncthing fork deleted their account and the repos out of the blue. There's a lengthy forum post about it here.