c-toxcore VS fdroiddata

See also this somewhat infamous thread on Tox's cryptographic design[1].

[1]: https://github.com/TokTok/c-toxcore/issues/426

In case with Tox you have to trust in homebrew crypto that was never properly audited (how about that security issue reported by Donenfeld in 2017, which is being tackled only now, sort of?) -- and outdated and outright abandoned clients which were never above, let's say, "beta quality".

it has the new group chat feature (https://github.com/TokTok/c-toxcore/pull/2269)

"If Tox already does onion routing, why use Tox over Tor?"

What an arbitrary criteria to judge a project by. There have been 5 releases in the past year, including a major feature release.

https://github.com/TokTok/c-toxcore/releases

Signal isn't falling behind and Tox is an old service that has had issues with messages being spoofable since day 1

tox https://github.com/TokTok/c-toxcore/issues/426

You could use a Tox front end like qTox or Toxic. It is a fully encrypted end-to-end communication protocol that allows text, voice, and video chat. The github page for the Tox protocol has some useful caveats about the its security.

It links to a bug report discussion where one of the developers states that they don't understand the security properties of tox very well[1].

I find that worrying.

[1] https://github.com/TokTok/c-toxcore/issues/426

Fork this repository.

For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183

You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.

To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).

OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400

You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.