this post was submitted on 19 May 2025
573 points (98.8% liked)

linuxmemes

25043 readers
2521 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 2 points 11 hours ago* (last edited 11 hours ago)
    [–] [email protected] 91 points 4 days ago (1 children)

    I'm something of a proprietary blob myself.

    [–] [email protected] 27 points 4 days ago (2 children)
    [–] [email protected] 13 points 3 days ago (1 children)

    You can get my source code but good luck compiling it.

    [–] [email protected] 19 points 3 days ago (1 children)

    9 month compile time?? We've gotta get these numbers down

    [–] [email protected] 12 points 3 days ago

    Just multithread. If you get nine people pregnant you can have a baby in one month, right?

    [–] [email protected] 6 points 3 days ago

    Ayy, not that fast, their blob is licensed under the BSL, get to know them a while first

    [–] [email protected] 17 points 3 days ago (1 children)

    something something snap package

    [–] [email protected] 6 points 3 days ago (1 children)

    Not a proprietary blob unless you install proprietary software

    [–] [email protected] 8 points 3 days ago (1 children)

    I'm mentioning the "proprietary backend" drama around snaps. Not that I care too much, anyway. I use lots of proprietary software daily

    [–] [email protected] 7 points 3 days ago* (last edited 3 days ago) (1 children)

    It isn't a "proprietary back end" it is what Stallman calls Service as a Software Substitute. (SaaSS) It wouldn't matter if they claimed it was completely foss. You are still using a foreign service you don't control.

    With a package manager that is sort of unavoidable though. In the case of snaps you could always modify the source to have a different repo. The real reason not to use snaps is all the other issues.

    [–] [email protected] 7 points 3 days ago

    Fair point. Just to be clear: I am NOT a developer, so I may be very wrong on that take.

    But from what I understand, the difference from what snaps does to what traditional packages does is that the Canonical repos are hard coded in it, thus making it harder to decentralise, and that's not very in line with what many wish for a FOSS ecosystem.

    [–] [email protected] 77 points 5 days ago (4 children)
    [–] [email protected] 122 points 5 days ago (4 children)
    [–] [email protected] 1 points 11 hours ago

    i been waiting for this so long

    [–] [email protected] 22 points 4 days ago (1 children)

    There is also a new community fork to get rid of the blobs and bad cert loading. The ventroy dev has made a bunch of concerning choices so some people hard forked the code. I forgot where is was though.

    [–] [email protected] 18 points 4 days ago (1 children)
    [–] [email protected] 7 points 4 days ago

    That's the one

    [–] [email protected] 42 points 5 days ago (1 children)

    oh wow that really put the trust back into Ventoy. Nice! Thanks for the link

    [–] [email protected] 16 points 4 days ago

    Happened after a partner product in the Ventoy repo was found to have a pretty major vulnerability due to a... you guessed it, pre-compiled supply chain attack.

    [–] [email protected] 2 points 3 days ago (1 children)

    Took them over a year to say anything? I have since just gone back to burning single drives and honestly it's fine. Ventoy was convenient but taking a year to respond to a genuine concern is crazy.

    [–] [email protected] 4 points 3 days ago* (last edited 3 days ago) (2 children)

    I'm going to guess you've never been part of a project with complexity and sheer black magic fuckery comparable to Ventoy. The developer (a singular person) had to make a choice between:

    • Pandering to a small group of vocal open-source extremists, dedicating a large part of their time to changing the incredibly complex build process to also build the binaries of other open-source projects, potentially at the cost of stability, eventually arriving at a product with the same feature set, pleasing some open-source extremists, but still receiving criticism for "taking a year to respond to a genuine concern"; or
    • Not doing that and focusing their effort on stability and compatibility fixes to arrive at an improved product.

    I've read the original issue thread front to back, and it's a fucking clown show. I can't blame the developer for not wanting to engage with those people. Nobody is entitled to the developer's time or attention. Right now the issue is being worked on, which is more than most of the whiners can say about themselves; if you think that's still insufficient, do better.

    [–] [email protected] 1 points 3 days ago

    Mr Ventoy has too many problems

    load more comments (1 replies)
    [–] [email protected] 22 points 5 days ago (2 children)

    just started using this for the first time, Is it still ok to use?

    [–] [email protected] 62 points 5 days ago* (last edited 5 days ago) (2 children)

    Yes, but people have concerns. Ventoy is fully open-source, but the build process pulls binary blobs (compiled executables, think of them like blob chips) from other F/OSS projects, which is an issue for some people. They have legitimate concerns about trusting Ventoy because they have to implicitly trust the projects that Ventoy pulls from but can't verify what is getting pulled. If such a project were to become compromised (the way XZ-Utils was), it would eventually spread to Ventoy.

    That being said, the developers (or singular developer, not sure) are taking steps to reduce Ventoy's dependency on external blobs. It's a difficult task and they have limited resources, but they have acknowledged that it is an issue and are working on a solution.

    [–] [email protected] 34 points 4 days ago* (last edited 4 days ago)

    If such a project were to become compromised (the way XZ-Utils was), it would eventually spread to Ventoy.

    What a lot of people don't know is that the XZ attack entirely relied on binary blobs: Partially in the repo as binary test files, and partially in only the github release (binary).

    If someone actually built it from source, they weren't vulnerable. So contrary to some, it wasn't a vulnerability that was in plain view that somehow passed volunteer review.

    This is why allowing binary data in open-source repos should be heavily frowned upon.

    load more comments (1 replies)
    [–] [email protected] 19 points 5 days ago (1 children)

    Yea it's fine.

    From memory the blob everyone was complaining about was related to eufi and came from Fedora.

    load more comments (1 replies)
    [–] [email protected] 7 points 4 days ago

    Just open source blobs instead of proprietary blobs

    [–] [email protected] 12 points 4 days ago

    Off topic, but I'd never heard of Ventoy before and looking at it now, holy shit, I wish I'd known about it sooner.

    [–] [email protected] 45 points 4 days ago (3 children)

    And here I am, marking unfree software as installable as the first thing I do on any distro.

    [–] [email protected] 26 points 4 days ago (2 children)

    It's good that it's opt in

    [–] [email protected] 9 points 4 days ago

    Oh, agreed. There are definitely people who can live without unfree software. Me, I can't do without Steam and Lutris.

    [–] [email protected] 2 points 3 days ago (1 children)

    The NixOS default config has allowUnfree set to false, so it's not always opt-in

    [–] [email protected] 1 points 1 day ago* (last edited 1 day ago) (1 children)

    That sounds changeable and off by default. So how come you wouldn't say that is opt-in?

    [–] [email protected] 1 points 1 day ago

    Unfree apps are not allowed by default. You have to opt in to allow them.

    [–] [email protected] 9 points 3 days ago* (last edited 2 days ago)

    I love OSS but I won’t sacrifice my experience just to go fully libre. Sometimes it just doesn’t make sense. I’m glad it’s an option for people who do want that though

    [–] [email protected] 9 points 4 days ago (1 children)

    I'll absolutely take FLOSS if I can get it, but failing that, FOSS is still a nice improvement over closed-source software.

    [–] [email protected] 2 points 3 days ago (1 children)
    [–] [email protected] 2 points 3 days ago (3 children)

    Libre, which is synonymous with free.

    I think it's more free in some way? I'm not sure, but I think it means free as in doesn't cost anything. Whereas FOSS means free as in open and modifiable, but the maintainer(s) might still charge for it.

    [–] [email protected] 5 points 3 days ago

    Its French for "free", as in freedom. Free is ambiguous and can also mean free of charge.

    [–] [email protected] 5 points 3 days ago (1 children)

    I think those are backwards

    [–] [email protected] 3 points 3 days ago

    I thought they might be... you're probably right.

    [–] [email protected] 1 points 3 days ago

    Libre means "with little or no restriction," whereas Gratis means β€œat no monetary cost."

    [–] [email protected] 23 points 4 days ago
    [–] [email protected] 13 points 4 days ago

    Linux moment

    [–] [email protected] 26 points 5 days ago

    Ah yes, telegram

    [–] baggins 25 points 5 days ago* (last edited 5 days ago)

    Unzips my ghidra 😏

    [–] [email protected] 4 points 3 days ago
    [–] [email protected] 16 points 5 days ago (2 children)
    load more comments (2 replies)
    [–] [email protected] 3 points 3 days ago

    If the working conditions don't change computers will become a ball and chain Then deemed useless.

    load more comments
    view more: next β€Ί