![](https://programming.dev/pictrs/image/2c69e418-9bd7-414a-a4fe-f09098123531.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
What about adding the flags last?
rm deletethisrepo -rf
What about adding the flags last?
rm deletethisrepo -rf
You could still NAT between v6’s though.
Strange, I don’t see this behavior on my device. Not sure what information would be relevant to debugging this though.
A few from Itch, Parallel Launcher from Flatpak for SM64 hacks
It’s probably the biggest deal for games running in xwayland
That’s a latrine. They’re talking about a fancy light fixture.
Also, monetization
How is it compared to wofi?
More people should be like you.
Exact same. Sway’s 1.0 release was March of 2019, and it did everything I needed.
Even playing games on my desktop, Xwayland worked fine for me.
Nope. If you open a nonexistent path and you have permissions to write to that directory, then that file is created.
8GB memory + two Firefox profiles makes things difficult on my laptop.
Others have mentioned disk usage and desktop integration. There is some truth to them, but shared runtimes keeps disk uasge down (although worse than native apps). Desktop launchers now search /var/lib/flatpak/exports/share/applications
by default, but I’m still having issues with themes in one or two niche apps.
Trust is the big one. The benefit of your distro’s packages is that they are maintained by a limited number of maintainers. Flatpaks have a much, much larger number of maintainers, which is where sandboxing comes in. Flathub now marks apps with lax permissions as “potentially unsafe”, which is a huge step in communicating this to the average user.
Most desktop apps can get away with having next to no access, as long as they support the appropriate XDG desktop portals.
Ultimately, your mileage will vary, as there are many classes of application which are ill-suited to being sandboxed. Program launchers, programming languages, IDEs, file managers are a few.
If you use EndeavourOS, know that you shouldn’t ask for support on the Arch forums, its a policy they have.
The upside of not changing the I/O is accessory compatibility.
Nope, confirmed different mobo.
I use the web version in Vivaldi, I’ve always had issues with video calls in Gecko.
It varies. Reddit is/was the primary forum for a number of projects, and as each sub is community moderated, could be quite rich, even if the whole is “generally full of garbage”.
I get your point. Since a .tar.zst
file can be handled natively by tar
, using .tzst
instead does make sense.
CSS is turing conplete.