• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: March 7th, 2025

help-circle
  • My personal suggestion would be to add initcall_blacklist=algif_aead_init to your kernel arguments. Ebpf is cool, but not a very trivial solution.

    I understand the suggestion might apply to a random, unspecified distro but I disapprove of both the exploit authors and the general Internet suggesting fixes that don’t apply to every distro (including copy.fail’s AI slop RHEL distro that doesn’t exist) without caveating it.

    The kernel module blacklist won’t work for every situation, if you’re not being specific in telling people where it applies, it’s best to suggest a solution that actually works regardless of distro or explain how to validate when it applies but nobody is doing that.



  • If you’d like evidence of the toxic or extreme side of Lemmy, it’s not hard to find. Are we really disagreeing that this is a problem with Lemmy? Regardless, you’re misrepresenting OP with the “declare the other side is unbiased”.

    This conversation started started with pushing back on the idea of using Lemmy as a solution to small site discoverability. The toxicity and social aspects are perfectly relevant.





  • If I’m a military supplier of nukes to the government, I can freely use GPL and there’s no legal issue with that. You cannot request the nuclear launch software or the guidance control software even if they use GPL licensed code within it. Why? Because they don’t distribute said code to the public. If you develop something for private use, and it never gets a public release there’s no obligation or requirement to release the source! This is especially true for a government contractor that only makes software for a single customer (the government).

    I think we’re agreeing that your claim was nonsense at this point, but I still don’t understand where people get these strange ideas about how GPL stops commercial or military use outside of very specific and frankly niche ways. If this is your reason for preferring GPL, it’s poorly thought out.

    In purely private (or internal) use—with no sales and no distribution—the software code may be modified and parts reused without requiring the source code to be released. For sales or distribution, the entire source code needs to be made available to end users, including any code changes and additions—in that case, copyleft is applied to ensure that end users retain the freedoms defined above.



  • StripedMonkey@lemmy.ziptoSelfhosted@lemmy.worldtest
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    5 months ago

    It’s unclear to me what you’re trying to achieve, and it seems like a counterproductive way to go about it, prone to failure, and needlessly expensive for anything of moderate size.

    You’re probably over indexing on the importance of downvotes if you’re just doing this for yourself. If you’re looking to make something actually useful to everyone, votes are probably an indicator of interest.

    Personally, I read the readme and concluded that that project wasn’t worth my time given the model and AI generated walls of text to tell me it has mobile accessible webpages and end to end encryption. Neither of which is a significant or revolutionary feature in 2025(almost 26) and are basically expectations.



  • This is incredibly reductive and at best looking at mumble through Rose tinted glasses.

    Mumble has had a rocky past as a useful piece of software and it’s absolutely not been a discord competitor any more than TeamSpeak is a discord competitor.

    Maybe it’s changed recently, but mumble has not had the feature set that made discord useful in the first place.