omapak is shipping IPFS Desktop as a Flatpak (the Flathub door got shut on it)

Open
#3,215 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
electron, javascript

Research direction

No repository file or test is named; the issue points to the external omapak Flatpak manifest and its review at outcrop-labs/omapak#10. Start by reviewing that manifest and the linked packaging report, then determine whether the project wants to endorse, take over, request changes to, or decline the third-party package.

Written by the indexing model from the issue text.

Description

Hey. I run omapak, an open Flatpak repo that exists because Flathub's 2026 policy bans new apps with any AI involvement in the submission. A community member's IPFS Desktop submission (flathub/flathub#10144) got closed over exactly that, which is how a 6.5k-star official client ends up with no Linux store presence. Dumb rule, so I built the alternative.

omapak now has IPFS Desktop in review: outcrop-labs/omapak#10. The manifest is that community submission, unchanged: your pinned v0.50.0 deb on the Electron BaseApp, x-checker-data wired so versions track your releases. It builds clean, and the agent judge's public report scored it honestly (the one advisory worth acting on: the report suggests disclosing the bundled Countly analytics in the appstream description, and disabling electron-updater inside the sandbox in favor of flatpak updates).

To be clear about the arrangement, Flathub-style: this is a third-party repack of your official release artifacts. If you'd rather own it, the submitter seat is yours and I'll step aside; if you want any changes to how it's packaged, say the word here; and if you want nothing to do with omapak, that's fine too, tell me and I'll drop it. If you ever ship an official Flatpak yourselves, we'll defer to it and close ours, same rule Flathub uses.

No questions about who or what wrote your code were asked in the making of this package.

— jon, omapak.org / the mission

Dominant language
JavaScript
Stars
6.6k
Forks
908
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ipfs/ipfs-desktop

All issues in ipfs/ipfs-desktop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.