• 1 Post
  • 66 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle



  • Probably a bit of a TL:DR of the other answer, but the short answer is: the execute bit has a different meaning for directories - it allows you to keep going down the filesystem tree (open a file or another directory in the directory). The read bit only allows you to see the names of the files in the directory (and maybe some other metadata), but you cannot open them without x bit.

    Fun fact, it makes sense to have a directory with --x or -wx permissions - you can access the files inside if you already know their names.

    Edit: not a short answer, apparently



  • If it is an Arch-based distro (sorry, I don’t recognize the package manager), then this might just be the recent Wine update that made it 700 MB smaller (which would mean the rest of your system grew 300 MB)

    I made a post here about it: this one

    Btw, is there a way to link to a post in a way that resolves on everyone’s separate instance instead of hard coding it to my instance?


  • Also, some programs, such as many terminal emulators, can cache you PW so you don’t have to enter it multiple times.

    Terminal emulators don’t (or at least shouldn’t) do any such thing. sudo itself is responsible for letting you do privilege escalation without password for some time after successfully passing once - whenever you run it and successfully authenticate, it saves your user id, current time and a session identifier (each open shell gets a unique identifier) into a file. Then, when you attempt to do anything, it will check this file to see if you’ve if you’ve authenticated within the last few minutes in this terminal, and only ask for a password if you haven’t.

    For more info, see man sudoers_timestamp


  • Markaos@lemmy.onetoPrivacy Guides@lemmy.oneCookies
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    As others said, configure your browser to store as few cookies as you can tolerate (because some actually useful stuff will break without them) and forget about these banners.

    Although I do enjoy the ones that have actual usable toggles for “legitimate interests” - how nice of them, giving me an option to disable even cookies they can legally store with just a notice, and definitely not just hiding non-essential cookies into a vaguely defined category.

    So I always go through the list and disable them one by one. It does nothing but waste my time, but I do it out of spite. Oh, and when I feel like really wasting my time, I send a bug report to whatever support email I can find on the site, about how the cookie banner accidentally let me disable essential cookies and should probably be fixed.


  • I’ve explained my reasoning for all the points I disagree with. Which one do you have a problem with? CS:GO? The last version of CS:GO is still available on Steam and fully playable, the only missing part is matchmaking servers - you can play with bots or on third party servers without any problems. That seems far from gone.


  • CS:GO got a controversial update and got renamed. Old versions are still available under CS2, you just can’t use Valve’s servers anymore. Playing old versions on private servers is possible. But OK, I give you half a point for this one - you can’t play matchmaking with old smoke physics anymore (but then again, it’s not like it’s the first CS:GO update to change the gameplay in a fundamental way).

    Moving on, Artifact. It’s in my library, ready to be played - Valve definitely didn’t “make me lose Artifact” like you claimed. The community is dead, but there are still 40 people playing right now according to SteamDB and servers are up. One point down for easily verifiable lie.

    And finally, Team Fortress 1. I assume you don’t mean the Valve’s game called Team Fortress Classic, because that one is still available for purchase on the Steam Store and oscillates between 40 and 100 active players at any time. So that leaves us with Team Fortress, a mod for Quake. But that one is available from ModDB without any problems, so… What’s the issue supposed to be, exactly? No points, because I have no idea if there’s more to your claim.

    Hint: blatantly lying about some points heavily undermines the other points you make. So at least try to be subtle.


  • It should not be controlled by a company that is known to make you lose your games.

    Are you referring to the fact that Valve promotes digital game distribution (which is a very fair view), or are you talking about some incident where Valve removed games from people’s libraries? Because if it’s the second one, then I would really like to hear about it.


  • Are you sure you didn’t set DNS directly on some/all of your devices? Because in that case they won’t care about the router settings and will use whatever you set them to.

    Also as the other commenter said, DNS changes might not propagate to other devices on the network until the next time they connect - a reboot or unplugging the cable from your computer for a few seconds is a dirty but pretty OS agnostic way to do that.


  • No worries, nothing wrong with not knowing everything about every random subject. I would like to apologize for being overly harsh, I assumed that people in c/opensource would have general knowledge of this definition, but that assumption was clearly bad. So again, sorry.

    I assume the term is misused often.

    Yes, companies sometimes do that. Open source is marketable as a guarantee that you won’t fully lose access to a piece of software, and there aren’t any real consequences of misusing it. But there’s also a scheme called dual licensing where the software is available under two licenses - one license is open source but annoying for commercial use, and the other is a “normal” proprietary license under which businesses can buy the code. This is fine (as long as the provider has copyright to all the code being dual licensed) and is pretty common and makes the software open source.


  • But “open source” doesn’t even mean that you can reproduce it or use it for free.

    You’re thinking of source-available licenses. Open source has a clear and widely accepted definition that requires a certain level of freedom. You’re free to ignore this definition, but you can’t expect the rest of the world to do the same.

    To be clear, open source allows for only providing access to paying customers, but those paying customers are then free to use and distribute their copies without any further payment. Then it wouldn’t be open source anymore.


  • I mean, it’s called “LaTeX by example”, so there’s a pretty good chance it’s written in LaTeX, which you do indeed compile to get the PDF or whatever output you want.

    Also, just having access to the source doesn’t make it open source - that requires more freedoms. For example, here’s GitLab Enterprise Edition source code, fully functional and ready to be used. And also officially described as the proprietary edition of GitLab by the GitLab company itself. Why? Because its license pretty much boils down to “you can use this only for testing and development, unless you have paid for it”.





  • Not a fair comparison IMHO - Ethernet is designed to be a connection between two or more otherwise independent peers (on L2), while USB’s goal was to allow connecting simple peripheral devices to computers. There was never meant to be a situation where it’s unclear which side is the Host.

    Also note that the bridging “cable” is literally just two USB devices, one for each computer (although they are both on the same chip, so there’s that), with some internal link to pass the data.


  • You could put your .desktop files in a separate directory and just symlink them to ~/.local/share/applications. If you want to have all your aliases together, you could have a directory like Aliases or whatever and then have Aliases/desktop for .desktop launchers, Aliases/bin for scripts or binaries (and have it in PATH), Aliases/bashrc for your bash aliases (and just put source .../Aliases/bashrc in ~/.bashrc), etc.

    Of course everyone has their own opinions on how to organize stuff, but this is IMHO pretty clean for what you probably want to do.

    Edit: and to quickly (re)create the symlinks, you could use a bash one-liner like for f in .../Aliases/desktop/*; do ln -s "$f" "~/.local/share/applications/$(basename "$f")"; done - put it into your bashrc as a function and remember to run it whenever you create a new .desktop launcher, and you should be golden.