Both, that’s why we’re moving to a zero trust model. Mozilla provides an official flatpak though so I don’t sweat it when it comes to how it affects my system as much as I would if it was on the host.
It’s not random, we check and choose things based on what we feel is appropriate to add. Can you be more specific? Things like VSCode are a compromise. We know it is, but it’s the best solution that we have right now until we can convince the right people to help fix it properly for everyone.
I don’t need to, who do you think is developing all the technology we’re consuming?
None taken, no worries.
The correct answer is to reconcile the Flatpak and Chromium sandboxes and get the engineers talking. We’ve actively tried to pursue and work to get the right people in the room. I’ve had calls with most of the major players, we’ve tried to chase down old patches to get upstream, and I’ve talked to people who could help fix the problem. The answer is always the same. No one has time to get this work done, empathetic to the problem, lack of resources. The Linux desktop will always be stuck at the bottom of every single engineering list as long as it continues to be a failure in the marketplace.
That’s just the reality of the situation.
I am on my fourth straight year of failing to move the needle on Flatpak/Chromium, I’m sorry that my personal investment into this has not yielded the results you were looking for.
Given the choice of dealing with the failure of the traditional model vs. fixing Flatpaks, I choose to help fix Flatpaks.