@ooops2278:matrix.org

Trying to centralize my fediverse use with kbin but still with (rarely used) accounts on:

Lemmy: @Ooops &
Mastodon: @Ooops

  • 0 Posts
  • 28 Comments
Joined 11 months ago
cake
Cake day: August 1st, 2023

help-circle

  • Ooops@kbin.socialtolinuxmemes@lemmy.worldLinux Salesman
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 months ago

    Canonical is basically the closed to corporate Linux you will find on the free distro market… They are pushing stuff you don’t want for marketing reasons (for example their own proprietary Snaps when a better working open source solution already exists with Flatpack), love their telemetry (can be mostly disabled for now, but given the defaults and their other behavior we can already see where this is heading) and in general decide more alongside their latest business plan than actually making sense or listening to users.






  • Ooops@kbin.socialtolinuxmemes@lemmy.worldI'm too afraid to ask
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    6 months ago

    Basically yes. Or: the term is fine; in the eyes of people who never heard or thought about its racist origin.

    And your were entirely on the right track when your first comment started with explaining the origin first. When that’s your starting point and you then get the response “But I’ve been saying it for years”, it’s probably far more successful to go with “Yes, but it can be offensive for people knowing its origin, so why not use available alternative terms?” than with “bro it’s been fucking racist for years”. In one case people have a high chance on thinking about it, in the other they will instictively feel attacked and get defensive about it.


  • Ooops@kbin.socialtolinuxmemes@lemmy.worldI'm too afraid to ask
    link
    fedilink
    arrow-up
    14
    arrow-down
    2
    ·
    edit-2
    6 months ago

    I just don’t understand why people are attached to it

    Because words aren’t racist, people and opinions and sentiments expressed by them are.

    When the term ricing is used for so long and 95%+ of people don’t know where it came from and have zero negative connotations associated with it, your argument (from their perspective) sounds like this:

    “Don’t use the term, by its obscure origin you didin’t even know about it is racist”

    “I’ve been saying it for years without any racism intended nor perceived

    “bro it’s been you are being a fucking racist for years”

    And then you are surprised by the negative reaction…







  • Yes, you can. But the usual setup is to have a file system root that is nothing but subvolumes, which you can then use and mount basically as if they were independent partitions. But when you don’t create a root subvolume for your system root first, you install the system directly on the file system root alongside created subvolumes. This tends to get messy as strictly speaking the file system root is a subvolume, too. So now you have that with your system installed and all other subvolumes nested inside it.




  • Ooops@kbin.socialtolinuxmemes@lemmy.worldThey caught us
    link
    fedilink
    arrow-up
    27
    arrow-down
    2
    ·
    7 months ago

    That’s defintiely the wrong title.

    No, it’s not the user catching Linux in trying to pretend user friendliness witht the terminal.

    It’s Linux catching the user in still hating it when he gets the wanted user friendliness, for the sole reason of being conditioned to hate the terminal.


  • Ooops@kbin.socialtolinuxmemes@lemmy.worldYou have no power here
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Of course not. There is a market for investing very little for some cheap malware and then putting it out there, waiting for the small amount of people (out of a billion of desptop users) falling for it. Also you go for the weakest link in defense, so scamming random desktop users is rarely a technical feat. It usually exploits the human, not the system.

    But we also all know how money is actually distributed. So millions of random users being scammed for some money is still not the high reward scenario a server is. Much more work is invested there because the rewards are so much higher. And yet even then you often target people as the weak link. System security for a company is mainly user security. Teaching them to not fall for for scams as an entry way to the system. And there are a lot of professionals that basically made this their own social science of how I convey those things the best, how I enforce and regularly refresh those lessons, how to make people stick to best practices.

    Are you trying to tell me this all happens in parallel to a technical server structure that actually isn’t that safe but rarely exploited because nobody could be bothered to check for vulnerabilities as it’s just Linux and the adoption rate is low?


  • The cruder the malware, the better your chances of running successfully in Wine.

    Because throwing together some simple executable using inbuild windows functions is much easier than programming something well-build and hidden based on deeper system layers. So your random “I just encrypted all your files because you clicked this .exe, now send me bitcoin to get it back”-bullshit might work well on wine (which is why wine should be run as it’s own user with no priviledges to access anything but your Windows programs).