Closed qoijjj closed 5 months ago
This is an unofficial repackaging. None of the maintainers have access to signal.org
to add the verification file.
Who do you want to be verified anyway?
This is an unofficial repackaging. None of the maintainers have access to signal.org to add the verification file.
Right but if you're open to it, it could be requested of upstream.
Who do you want to be verified anyway?
I don't understand the question
I use secureblue
and one of the hardenings that it applies is to only allow flatpaks from flathub-verified
.
It is quite outrageous that a non-official Signal client is verified, e.g. Flare, and Signal Desktop is not.
The official developers don't care about flatpak. 🤷
(Time-wise, I'm not judging.)
You could buy the domain signal-flatpak.org, verify it, and add it here.
@storopoli please see this, this, and most importantly this. Please do not reference secureblue in upstream reports especially for tickets like this which aren't even scenarios recommended by secureblue, as it reflects badly on the project.
Upstream devs aren't interested in verification, so this ticket should be closed and possibly locked at this point.
Getting verification would allow an increased level of user trust.
https://discourse.flathub.org/t/how-do-you-get-a-flathub-submission-verified/3714 https://flathub.org/apps/collection/verified/1
I believe this would require the blessing of upstream devs via hosting a file.