Open bunnybot opened 11 months ago
Mirrored from Codeberg On Thu Dec 28 14:53:19 CET 2023, Tóth András (tothxa) wrote:
I was able to generate the token. I guess it's like a public key, as it's supposed to be posted at a well known URL, so here it is:
9773ed19-f742-45a7-9ecf-2108d1ab7ae3
I'm not sure how long it will be valid though, because the next step at flathub when I click continue tries to fetch the VerifiedApps.txt
file from widelands.org.
Mirrored from Codeberg On Thu Dec 28 15:02:14 CET 2023, (frankystone) wrote:
Didn't we need two tokens? One for beta and one for stable?
I think it's more secure if you send me this token as PM…
Mirrored from Codeberg On Thu Dec 28 15:56:02 CET 2023, Tóth András (tothxa) wrote:
I think flathub-beta is meant for testers only. AFAIK beta builds are not advertised neither on the main flathub.org site, nor any other place. That's why I like to post on WL.org when I do an update. (oh, yes, last night's update should've already been announced :)
Otherwise it's treated as the same project (just another branch in the github repo), and they only listed a single entry for Widelands in the developer settings page.
Mirrored from Codeberg On Thu Dec 28 16:09:52 CET 2023, Tóth András (tothxa) wrote:
I checked the token creation again, and it gave the same token.
Mirrored from Codeberg On Thu Dec 28 17:53:03 CET 2023, (frankystone) wrote:
Should work now: https://www.widelands.org/.well-known/org.flathub.VerifiedApps.txt
The implementation might get changed in the future, but the URI will not change.
Mirrored from Codeberg On Thu Dec 28 19:23:25 CET 2023, Tóth András (tothxa) wrote:
Thank you. I was able to finish the verification process on flathub, and Widelands is now listed as verified.
Mirrored from Codeberg On Thu Dec 28 19:26:20 CET 2023, (frankystone) wrote:
I'll leave this open until the final changes were committed
Mirrored from Codeberg On Thu Dec 28 19:58:55 CET 2023, Benedikt Straub (Nordfriese) wrote:
Thanks :)
Mirrored from Codeberg Created on Thu Dec 28 12:42:28 CET 2023 by Benedikt Straub (Nordfriese)
It would be good to verify our flatpak package's connection to our homepage. See https://docs.flathub.org/docs/for-app-authors/verification/
Basically, Flathub would provide a unique token and we'd have to place this token in a plaintext site https://www.widelands.org/.well-known/org.flathub.VerifiedApps.txt to show that the flatpak package is officially provided by us.
<@>tothxa <@>frankystone