flathub
com.visualstudio.code | flathub | |
---|---|---|
36 | 114 | |
124 | 1,065 | |
0.0% | 1.7% | |
7.5 | 6.7 | |
15 days ago | 5 days ago | |
Shell | ||
- | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
com.visualstudio.code
-
Fedora Workstation 41 to No Longer Install Gnome X.org Session by Default
vscodium flatpak fonts are already fine; IME vscodium works with font scaling fine out of the box. There's a vscode flatpak issue: "Feature: add optional Wayland support" https://github.com/flathub/com.visualstudio.code/issues/471#...
https://news.ycombinator.com/item?id=39625917#39637408
- Dualbooting windows vs. virtual machine
- Flatpak launching external program
-
How to make flatpak IDEs detect system interpreters
The VSCode flatpak README has some solutions:
-
Cannot open visual code on command line using "code" and "vscode"
Otherwise, you could install the flatpak version from Flathub and that alias would start doing what it's intended to do: https://flathub.org/apps/details/com.visualstudio.code
-
what is the best way to install apps in fedora?
For VSCode, it looks like you need to do a little bit of work to get it working properly in Flatpak. Everything should work if you put in the elbow grease, but this is one of those examples where Flatpak makes things a bit funky for people unfamiliar with how it works, and it doesn't help that Microsoft doesn't officially support the Flatpak.
- I can't install VS Code
-
VS Code Settings for Flatpack
Please open issues under: https://github.com/flathub/com.visualstudio.code/issues This version is running inside a container and is therefore not able to access SDKs on your host system! To execute commands on the host system, run inside the sandbox:
- Flatpak version of vscode is showing this error..... I cannot login to github account and sync settings
-
Debug Golang com VSCode
VSCode versão 1.74.1 instalado via flatpak;
flathub
-
XZ backdoor story – Initial analysis
> Nobody ever even audits the binary contents of flatpaks on flathub (were they actually built from the source? the author attests so!).
IME/IIRC There aren't (or shouldn't be) any binary contents on Flathub that are submitted by the author, at least for projects with source available? You're supposed to submit a short, plain-text recipe instead, which then gets automatically built from source outside the control of the author.
> The Flathub service then uses the manifest from your repository to continuously build and distribute your application on every commit.
https://docs.flathub.org/docs/for-app-authors/submission/#ho...
Usually the recipes should just list the appropriate URLs to get the source code, or, for proprietary applications, the official .DEBs. Kinda like AUR, but JSON/YAML. Easy to audit if you want:
https://github.com/orgs/flathub/repositories
- FOSS software is probably less likely to abuse this, but it just depends how ruthless the publisher is, a lot of people desire to be successful and it's human nature to look for advantages to put yourself above others in competitive environments.
-
Flathub – The Linux App Store
I also don't believe third parties maintainers packaging software on flathub is a big issue but I'm also not familiar with how other distro repos trust their maintainers. Hopefully more developers maintain their flatpak themselves (or someone they trust) and get their apps verified. If most apps are verified, warning users of unverified apps might be a good idea.
There's ongoing discussion about splitting open source and proprietary apps in to seperate repos [1]. Additionally having seperate repos for verified and unverified apps might make it more obvious where an app comes from in the cli.
But I don't know how seamlessly an app could transition between being in the third party repo and being in the official repo. Having the user quietly stop receiving updates seems like a bad idea, but automatically migrating might not be desirable either.
I also think flatpaks cli interface needs some work. It is functional but far from distro package managers.
Being verified is especially important for critical apps. Recently someone added malicious versions of apps to the snap store [3]. This lead to people getting their cryptocurrency stolen.
[1] https://github.com/flathub/flathub/issues/691
[2] https://docs.flathub.org/docs/for-app-authors/requirements
[3] https://forum.snapcraft.io/t/temporary-suspension-of-automat...
-
Bforartists Flatpak, coming soon to Flathub
That means Linux users can now install Bforartists on any Linux distro easily, regardless of glibc version! https://github.com/flathub/flathub/pull/4295
-
Turtle 0.3 released (formerly TurtleGit)
Still having some problems with the flathub build, see https://github.com/flathub/flathub/pull/4082 for the current status.
-
TurtleGit released, a git frontend for GNOME and Nautilus
Here is the flathub draft pull request: https://github.com/flathub/flathub/pull/4082
-
The first tip to give to any new Linux user should be "do NOT search for, download, and install software on the Web!"
i assume you dont know how flathub works , theirs little or no QC , done flathub is just get told theirs an update for the package , if yo go look at the github repo pes https://github.com/flathub/flathub/pull/4164 for example , only updates the link to the girt repo , theirs 0 code checked
-
Who is behind flathub and rpmfusion really?
It all should be written in pages for contributors, read the docs for fusion, and the docs for flathub.
-
Flathub just hit 1 billion total downloads
These are criticisms of the flatpak ecosystem as it stands today. Currently, the Firefox ESR package on flathub seems to be caught in limbo or maybe dead. Mozilla publishes both a snap and a flatpak of Firefox latest, but only a snap of the ESR version. This raises the question of why. Have Mozilla chosen to invest more in snaps than in flatpaks? If so, what's their reasoning? (More users on snaps, making it similar to why they put more investment into Windows than Linux? Something else?) If they haven't invested more into snaps than flatpaks, is this a sign that it's harder to maintain flatpaks (or at least on flathub) than snaps? If that's true, I would hope that flatpak/flathub would be soliciting feedback from Mozilla about it.
-
VirtualBox as Flatpak
Because that may be very hard to sandbox: https://github.com/flathub/flathub/issues/3366
What are some alternatives?
net.lutris.Lutris
ZeroTier-GUI - A Linux front-end for ZeroTier
com.valvesoftware.Steam
Ryujinx - Experimental Nintendo Switch Emulator written in C#
com.sublimetext.three
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
flatpak-vscode - Integrate Flatpak with VSCode
flatpak - Linux application sandboxing and distribution framework
org.telegram.desktop
openbsd-wip - OpenBSD work in progress ports
org.videolan.VLC
steam-runtime - A runtime environment for Steam applications