Publish to Flathub

[BredMan0]

Summary

I know that this automatically builds a Flatpak and it would be great to have it published on Flathub. Publishing on Flathub allows for easier installation and makes it more accessble to more users, which can benefit the software with more people using it.

Basic Example

Publishing to Flathub.

Drawbacks

None apart from the work required to publish the application.

Unresolved questions

No response

[RayJW]

This would definitely be great! I outlined some more advantages for publishing in #423.

[viggy96]

Has there been any thought to publishing Fladder to any Flatpak remote?

[viggy96]

If there is any reason to NOT publish, I'd like to know.

[viggy96]

I have some users who are less experienced, it would help greatly to simply have this app be published on Flathub, therefore allowing users who are not very experienced at all to install Fladder easily, as it will be able to be installed entirely graphically.

And the client would stay updated automatically.

[viggy96]

If there is no interest from the developer, others may submit Fladder to Flathub themselves.

[PartyDonut]

There is a interest just no time at the moment. Or at least not to focus on this.

[CaptechOmar]

That would be awesome.
Any news on this?

[schembriaiden]

This is in progress (flathub/flathub#7123), I am just waiting for the next update, as there was a bug with the metadata which is fixed in the next release and then we see what happens from then onwards.

[schembriaiden]

@PartyDonut I need you to add an empty file to this location in your website for now in order for flathub to verify ownership after the package has been added, if that is possible:

https://jknaapen.nl/.well-known/org.flathub.VerifiedApps.txt

flathub/flathub#7123 (comment)

[schembriaiden]

Strange maybe a caching issue? Can you try curl -I jknaapen.nl/.well-known/org.flathub.VerifiedApps.txt

~
❯ curl -I jknaapen.nl/.well-known/org.flathub.VerifiedApps.txt
HTTP/1.1 301 Moved Permanently
Date: Thu, 16 Apr 2026 14:24:03 GMT
Connection: keep-alive
Location: https://jknaapen.nl/.well-known/org.flathub.VerifiedApps.txt
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=SjAlg2BrxxrZc4to4fEtCDACNOMls696%2Bxtsa2NCzdsdSrfwOqr9snACTeTMYz%2BRJidkXABeiNJtR8ndXEkOfpvSLtHeMNQAgumCR2RrdTNiIznzYdLZ9JdmguKZfQ%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Server: cloudflare
CF-RAY: 9ed3d9f8586df940-MXP
alt-svc: h3=":443"; ma=86400


~
❯

[PartyDonut]

Very strange this is what it's reporting on my end. I will have a look if there is anything I need to change.

HTTP/2 200 date: Thu, 16 Apr 2026 14:30:01 GMT content-type: text/plain content-length: 0 server: cloudflare last-modified: Thu, 16 Apr 2026 13:46:14 GMT etag: "69e0e826-0" strict-transport-security: max-age=63072000;includeSubDomains; preload accept-ranges: bytes cf-cache-status: DYNAMIC report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=4cniQ3cuk8vI3LLPS1oAcLwhMH8PUhjZy%2FaKGOAWgCRaQVwjd4%2Fa9hbKBm1X9wT5okUBa9Kgbe2l6NPUvc%2FofblvNAd0t4aY%2FoktKzFPHD4kdhwKOj9Jac7iXNwvAA%3D%3D"}]} nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} cf-ray: 9ed3e2b39f5bfba5-AMS alt-svc: h3=":443"; ma=86400

[PartyDonut]

@schembriaiden Can you check again I cleared the cloudflare cache and added an exception for the .well-known folder.

Might still be caching issue somewhere else though but https://check-host.net/check-http?host=https%3A%2F%2Fjknaapen.nl%2F.well-known%2Forg.flathub.VerifiedApps.txt it seems to work using check-host.het

[schembriaiden]

@schembriaiden Can you check again I cleared the cloudflare cache and added an exception for the .well-known folder.

Might still be caching issue somewhere else though but check-host.net/check-http?host=https%3A%2F%2Fjknaapen.nl%2F.well-known%2Forg.flathub.VerifiedApps.txt it seems to work using check-host.het

Still the same for me everywhere 404 on the site itself and 301 using curl, tried on my phone too and it was the same.

EDIT: I found the issue for the 301, it is because it is a redirect to the https, when using this it worked: curl -I https://jknaapen.nl/.well-known/org.flathub.VerifiedApps.txt

[schembriaiden]

@PartyDonut, the Flathub repository has been created. I'm not sure whether you received an invitation to it, but I've sent an email to your support address containing the verification token for the app just in case you don't already have access to the repository. I wasn't sure if the token should be kept private or not 😄.

If you do have access to the repository, you should be able to verify the app yourself by logging into the Flathub website and accessing the developer portal.

If you didn't receive an invitation, I'd recommend opening an issue here to request access, since you're the primary maintainer. In the meantime, I'll continue helping maintain it as well, since I'm already familiar with how everything is set up and can help keep things running smoothly.

This is the repo: https://github.com/flathub/nl.jknaapen.fladder

[mbnoimi]

+1

Flatpak/Flathub is vital for me. I don't -and will never- install any app outside of Ubuntu/Debian and Flathub repositories.

[viggy96]

@schembriaiden What's blocking Flathub publication at the moment?

[schembriaiden]

The app has just been added, you can install it through here: https://flathub.org/en/apps/nl.jknaapen.fladder

or doing:

flatpak install flathub nl.jknaapen.fladder

[CaptechOmar]

Why is it unverified?

[schembriaiden]

because it just got uploaded and the app can only be verified after it has been uploaded. I am waiting on PartyDonut to verify it.

[CaptechOmar]

Got it
Thanks

[schembriaiden]

@CaptechOmar it has been verified now.

[CaptechOmar]

Awesome