• 13 Posts
  • 165 Comments
Joined 1 year ago
cake
Cake day: February 10th, 2024

help-circle


  • I can’t tell from that error message whether the inner quotes are being discarded when the command is run, or just hidden when the error message is displayed.

    Too bad it doesn’t tell you what part of the command is causing the syntax error. Have you checked for more info in the output of journalctl --boot _UID=1000? (Assuming your user id is 1000 and you use systemd.)

    Re-reading the spec page that I linked above, I see reference to both a general escape rule and a quoting rule. That could be complicating things with the quotes and backslashes, and maybe even the dollar signs and semicolons, which apparently are reserved. In case it helps, I don’t think those semicolons are needed at all.

    Before diving deeper into escaping rules, though, I would consider whether it’s time to move the whole command line into a script, and simply pass %f to the script in your Exec= line. That would avoid the need for nested escaping/quoting, and allow you to write debug information to a temporary file when the script runs.




  • As someone who runs multiple desktop sessions at once, each on a different virtual console, sddm is a continual pain in my workflow. Notably:

    • It assigns desktop sessions to virtual consoles inconsistently, and has no way to manually configure them, so Control+Alt+FN often switches to a session that’s not the one I wanted. The assignments can change from day to day or any time a session logs out and back in. This makes using multiple desktops a constant pain.
    • I don’t know for sure, but I suspect it is behind the graphical glitch that makes the desktop session unlock screen draw incredibly slowly on KDE 5. Having to wait several seconds for each character in my passphrase to register is an annoying waste of time.







  • What about the anti lgbt stuff? Thoughts…?

    It is important to remember that turning down a pull request does not make a person (or project) anti-LGBT.

    Sadly, I have seen bullying and brigading from people who claim to be supporting inclusiveness, more than a few times. That behavior alone would be enough to sour me on them personally, and on any change they had submitted.

    And, of course, there are other perfectly valid reasons to decline a PR as well.

    Asking for changes we would like to see is fine. Demanding them is not. Resorting to character assassination when we don’t get what we want is absolutely not.


  • I think it’d be great to live in a world where this technology required warrants, transparency, and other oversight from the start.

    Me too.

    It boils down to the fact that this technology is widespread, and will continue to be widespread regardless of my actions

    That same reasoning has been used innumerable times throughout history. I suppose each of us must decide whether we think it holds water. It reminds me of an old adage: No single drop believes it is responsible for the flood.

    Predator does way more than just ALPR.

    I know. I looked it up. I mentioned the name not because I think it represents what it does, but rather to point out that it will affect how people feel about you and your work, even if in subtle, imperceptible ways. It’s up to you to decide whether you’re comfortable with that.


  • I don’t have a specific suggestion, but here is what comes to mind:

    • Violation of human rights and civil liberties in order to gain power over others is always justified with noble-sounding excuses like protecting people and property. The reality does not match the claim.
    • Once violated, privacy of information is almost impossible to restore.
    • Anything that can be abused to someone’s gain will be abused eventually, if not immediately.
    • Relying on a benevolent gatekeeper (even yourself) to prevent abuse of your tech will eventually fail.
    • The name V0LT Predator evokes the feeling that it’s something the world needs less of, not more.

    Whenever I find myself on a fine line like the one you’re trying to walk, I consider whether I’ll look back on my life and be proud of what projects/causes/changes to the world that I advanced with the time and talents that I have.




  • Look for an instance with these qualities:

    • Does not use Cloudflare or any other large content delivery network. Instances that use thse allow the CDN to monitor everything your read and write on Lemmy, which can reveal a lot about you even if you haven’t used your real name. Cloudflare can then correlate that information with your other browsing habits, and possibly your real identity, because they operate as a middleman for a huge number of popular web sites.
    • Maintains a sizable local image cache. Images served from other instances instead of your local one can be abused by remote parties to track what is viewed on Lemmy with your IP address (and sometimes your browser signature). Alternatively, you could block off-site images using a browser extension, but that would mean not getting to see as many pictures.