Inbred: chaorace’s family has been a bit too familiar. (Can be inherited)

Expand?

  • 4 Posts
  • 162 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
  • It’s always a treat to see the wheels of open source & community funding meshing together to bring about a better internet. You and @nutomic@lemmy.ml have already done the honors of thanking the open source contributors, so I think it’s now my turn as an ordinary user to thank you both for your continued hard work and leadership – I have my quibbles, but these do not preclude the giving of a well-deserved and hearty thanks: Thank you! It continues to please me greatly to have the privilege (in both senses of the word) to contribute to the financial sustainability of the project as one of its many small recurring donators.

    And, while I’m at it… since the opportunity doesn’t come up often: I also want to specifically express gratitude to dessalines for their (unrelated) work on the thumb-key project. As a long-time user of MessagEase (10+ years!), I’ve become a happy convert to your more well-maintained and open source replacement. So, thanks for that too! Please continue to suffer my past & future criticisms with the knowledge that it always originates from a place of equal parts respect & gratitude.


  • When it comes to Deep Rock/co-op I think my issues are more associated with the underlying gameloop design. I find it hard to perform well when the “tension” ramps up and these games are kind of tailor-made to create high-tension situations. When a round ends I’m left feeling tired/deflated rather than joyful. I had the same issue with Left 4 Dead, but oddly not so for Payday 2.

    In any case, I’m right there with you when it comes to TF2 community servers. I sorely wish that more games emphasized these sorts of digital “3rd places”. I have TF2 servers where I can go anytime and just… belong for as long as I please. Games should have more permanent places like that, where play and community come before any imposed win/lose dichotomy. People would be happier.


  • Exactly. Making the game WINE-compatible is not the same thing as committing to support. In reality, the only thing stopping WINE from working is Epic Anti-Cheat and the absurd thing about this is that Epic already gave EAC a WINE-compatibility mode – they’re just actively choosing not to turn it on.

    What Tim’s really saying is this:

    I don’t want our flagship game to be used as a way to highlight Steam’s better Linux support, so the game won’t come to Linux until EGS on Linux is at parity. Unfortunately, it doesn’t make sense for us to bother doing that right now because the Linux usershare is too small to matter.



  • I had a really solid year, all things considered:

    • Hi-Fi Rush – Love it, hands down. This game’s like if Jet Set Radio, Scott Pilgrim, and DMC got into a fist fight and then that fist fight had a baby with Jack Black
    • Pentiment – I’m still playing through this one but I can already tell it’s a new favorite. Major Return of the Obra Dinn vibes
    • Against the Storm – This game innovates on the citybuilder genre so hard and I can’t get enough of it. If you love a challenge and hate the late-game, this is THE ONE
    • Psychonauts 2 – Fun and bursting with creativity… but I had to set it down after a certain point because I stopped enjoying the gameplay loop. Can’t put my finger on why…
    • Peglin – Yes, Peglin. The Peggle Roguelite. I like it and you would too if you gave it a chance. It’s not a forever roguelite, but I guarantee you’ll have a blast with it for 5-10 hours
    • Deep Rock Galactic – I bounced off of this one. The game has so much charm… but I just couldn’t click with it. I think co-op games just may not be for me

    Honorable Mention: TF2 – Definitely not a “new” game to me, I own TF2, I bought it with money! Even so… this year marked my return after a looong hiatus. Coming back was a total revelation – I thought I’d grown to hate FPS games – as it turns out, what I’d actually grown to hate was the modern antisocial MMR grindset. Game developers: I beseech thee… abandon matchmaking and return to 2007. Return the slab or suffer my curse


  • I think it’s a little unfair to escalate my talking about a presumably invisible and flavorless level of contamination into somehow advocating for choking down soot-blasted cancer nachos.

    For the record: that’s not what I meant and I think any reasonable person would not have interpeted it as such having read the context of the post. It’s a sealed bag of chips – they have functioning taste buds and eyeballs for Pete’s sake!





  • Wayland is Wayland. If you use a Wayland compositor, you’re getting a lot of security by virtue of design alone. Things like keyloggers and screenrecorders will not be able to intrude on your session barring vulnerability exploits. I’m not going to touch on the relative vulnerability risk of each environment since a) they’re all relatively new & b) I’ve never implemented Wayland myself

    With that being said, here’s what’s not protected by Wayland regardless of the chosen compositor: microphones, webcams, keyrings, and files.

    For microphones & webcams, any distro which rolls Pipewire in combination with Wayland will be sufficient to secure these. Pretty much all Wayland environments roll Pipewire so this is only important to consider if you’re running your own customized environment (be sure to disable any pre-existing PulseAudio daemon after setting up Pipewire to close this security hole)

    For keyrings, these are handled by your environment’s polkit implementation. Much like Wayland, there are several implementations of polkit and they’re all just about equally secure barring any potential vulnerabilities… Just make sure that you’re using an encrypted database (usually on by default) and that you have it configured to always relock & properly prompt for the unlock key.

    For file access, this is actually a core probelm with Linux as a whole – any unsandboxed application you run will be able to read any file that you can read. The solution is to use sandboxed applications whenever possible. The easiest way to achieve this is through using flathub/flatpak applications, since they will always list out and enforce their required permissions on a per-application basis. For non-flatkpak applications, you’ll need to use “jail” environments (e.g.: bubblejail, firejail) in order to artificially restrict application permissions by hand.


  • chaorace@lemmy.sdf.orgtoComic Strips@lemmy.worldEyyyyy macarena [ADHDinos]
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    4
    ·
    1 year ago

    Let’s put it this way: if you took out someone’s liver, would you say that the person is the sum of their parts minus a liver? If so, then congratulations that’s also how it works for ADHD. There is a pathology and that changes how the mind works. To argue otherwise would be akin to arguing that people without livers should just metabolize harder.




  • Not a dumb question! This is what I’ll have to do if no better solution comes around.

    The reason I haven’t already done that is that the underlying Holo code is not designed for multi-user. I won’t be able to just swap out the credentials because doing so will cause it to blow up when it fails to edit old posts owned by the old bot account. In other words: it’s going to be a big hassle to move over and even in the best case scenario things will break and generally look ugly.