I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 3 Posts
  • 731 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle

  • Sure but that requires the given parser (the web browser, the image lib, etc) to arbitrarily run code in the first place. Which… well, why? It’s an image, not a program. Treat it as an image. Hence “only an idiot” writes an image parser to actually execute an image (same with eg.: only an idiot would write an MP3 parser that arbitrarily executes an MP3).

    Even if an SVG had JS in it, as an image-proccessing lib the correct method would be not to try to run the JS in your SVG by yourself but rather just hand it down to whoever is processibg JS at the moment (which would be, well, the browser context and its sandbox).









  • Problems Linux itself has to overcome? Maybe two or three.

    • Hopefully I’m mistaken but apparently accessibility has been going down the last few years.
    • Settings that make sense to change should be exposed more adequately. No one should ever get a visual toggle to eg.: disable SELinux on their systray, but controls to adjust color profiles and screen “temperature” management should be more reachable and clear.

    Problems that are mistakenly attributed to Linux but that are actually for manufacturers, sellers and provisioners to take responsibility for and overcome? A good lot.

    • Sellers have to sell machines with Linux preinstalled. Getting a machine Linux-ready from factory is easy, but it’s only the commerces who can actually place them on a, ta know, selling point.
    • Sellers or manufacturers should actually advertise when their device works with Linux. If people have to guess whether their next buy even boots / plugs in, that’s a hindrance to commerce.
    • Hardware manufacturers are not providing adequate Linux support (FizzyOrange mentions the eternal issue of laptop battery management; Naiboftabr mentions stuff like “audio stops working”).
    • Developers have to get back to developing for Linux natively (rather than eg.: “develop for a trimmed down Windows version that runs on Steam”).
    • Developers of Linux itself need to provide a better “rescue mode” for when things inevitably go wrong. Something that boots up to a “guaranteed working state” that still has workable UI but with most or all customizations disabled.

  • A container runs the utility in an isolated environment without having to alter your base system’s packages, dependencies, etc. Assuming the bork that necessitates a reboot is not a kernel or hardware issue, this would mean that if you get hit with that issue again in a container, what dies is the container itself, rather than your system as a whole. So you’re isolating 1.- package management 2.- network config and (potentially) 3.- “blast radius”.

    (That said, this is the first time I’ve ever heard that Proton would bork the networking to the point of requiring a whole system reboot.)






  • lambalicious@lemmy.sdf.orgtoLinux@lemmy.worldDebian 13 releases today
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    8
    ·
    4 days ago

    I heard it was shipping libraries that capture all clipboard data and sent it to foreign servers unencrypted, and that this was being defended in the buglist as a feature, so I might actually skip this one at least until the first or second batch of security updates rolls on.

    For servers, it makes not much difference for me; where possible I either stick to Stable + Backports (which requires Backports in the first place) or jump right to Unstable.