Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unverified Flatpak? #699

Open
GalacticSun opened this issue Nov 5, 2024 · 4 comments
Open

Unverified Flatpak? #699

GalacticSun opened this issue Nov 5, 2024 · 4 comments

Comments

@GalacticSun
Copy link

I've noticed the Flatpak version of Fluent Reader is "unverified" (in the Linux Mint 22 software manager, for example).

Any chance this can get "verified"?

Thanks.

@GalacticSun
Copy link
Author

By the way, is anyone working on this application anymore, or has it been abandoned?

@grvn
Copy link

grvn commented Nov 20, 2024

@GalacticSun it seems like nothing is happening with this project.
I really like this application but it seems to be having a bit of issues with updating, a couple of dependencies in its flatpak packaging are starting to trigger warnings about deprecation.

Maybe time for a fork?
I'm unfortunately not a JavaScript developer so I'm not going to be able to do any good work forking it...

@GalacticSun
Copy link
Author

@grvn Yes, it's a shame. Hopefully someone will fork it.

@molytov
Copy link

molytov commented Mar 2, 2025

Ancient issue I know, but I figured I could offer an answer to the original question in case anyone else wonders.
Flatpak verification means that the release is handled by the developer(s) themselves or someone they give explicit trust to do it for them, while unverified applications are done by some independent volunteer(s).
There's not much that can be done to resolve dependency issues if upstream development (this repo) halts, and therefore no updated Flatpak releases to submit.
There doesn't appear to be much indication that Liu is coming back to keep working on this any time soon, and that they would also be willing to go through the process sorting out a verified release.

I would personally rather see more options that aren't just yet another electron app, so I can't say I'm totally in favor of a fork over a whole new project that isn't electron-based, although I do understand the former would be easier for development and existing users who want to stick with a familiar UX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants