this post was submitted on 27 Dec 2025
1098 points (96.9% liked)

Microblog Memes

9963 readers
3771 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] The_Decryptor@aussie.zone 4 points 4 hours ago* (last edited 4 hours ago)

So there's a couple of sources, like the (rather outdated) Mozilla wiki page detailing the sandbox support on Linux.

And I know it's specifically the Chromium sandbox, since they vendor their copy of it.

I also just checked the sandboxing status directly in Firefox.

And I'm kinda of cheating, I knew they used it since I've got an unsupported configuration with HW video decoding. It's caused by their sandbox blocking certain things, and it's a known issue. Nvidia drivers don't support VA-API, Firefox only supports VA-API. There's an adapter library available, but it doesn't work in Firefox unless you disable the sandbox.

Edit: Oh yeah, Firefox is also affected by the same issue Chrome is, where Flatpak interferes in the sandbox.