• 0 Posts
  • 554 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle





  • kautau@lemmy.worldtolinuxmemes@lemmy.worldI love snap /s
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    4 months ago

    The biggest issue to me with snap (unless something has changed since the last time I looked it up) is that it’s all a walled garden by canonical and it’s not open source (in the sense of package submission, review, rating, source availability, etc).

    With flatpak/flathub you can see the source and discussion behind each package

    https://github.com/orgs/flathub/repositories

    But that transparency doesn’t exist on snap so you are just hoping canonical did their homework on vetting apps






  • Bills can have only one subject. The subject needs to be the title. The title cannot be changed.

    And perhaps the title should be what the bill actually is

    For example something like “Freedom for American Internet Choice”

    Which likely removes regulation or restriction on a company being a monopoly because the “Freedom” is who can bribe the most and lobby against possible commercial or municipal competition.

    There’s plenty of bills like that where the title is incredibly misleading, on purpose, to get people who don’t care to do any research to wonder “why would anybody be against freedom?”



  • It’s literally how scammers scam people every day too. Just open up command prompt and run

    tree c: /f
    

    And say it’s them visualizing the hacker, or scanning for viruses or something stupid.

    Most people today do not understand computers at all. Even those freshly graduating with CS degrees often have little to no knowledge of how their OS’s work.


  • Lol yeah working in enterprise software for a long time, it’s more like:

    1. Import what you think you need, let the CI do a security audit, and your senior engineers to berate you if you import a huge unnecessary library where you only need one thing
    2. Tree shake everything during the CI build so really the only code that gets built for production is what is being used
    3. Consistently audit imports for security flaws and address them immediately (again, a CI tool)
    4. CI

    Basically just have a really good set of teams working on CI in addition to the backend/frontend/ux/security/infrastructure/ whatever else teams you have