• 151 Posts
  • 1.02K Comments
Joined 8 months ago
cake
Cake day: February 10th, 2024

help-circle






  • It’s middleware for game launchers like Lutris, but specifically for Wine games. It uses GloriousEggroll’s custom Proton builds instead of stand-alone Wine/DXVK/etc.

    Note that GloriousEggroll more or less discontinued his custom Wine builds, and has been encouraging people to use his Proton builds via this tool instead. It might make things easier or harder, depending on your needs and workflow. I expect it will be easier for casual Linux users when combined with a GUI.





  • And Perl both still exists and is actively maintained, so it “lost prominence” rather than “died”.

    Okay, but you’re the one who called out “the demise of Perl”. Have you changed your mind? I was just responding to your question.

    For what it’s worth, I think you were right about that: Perl is dead, in the sense of no longer growing or even maintaining the reach it once had. Other languages are overwhelmingly chosen for new code, while Perl has mostly fallen into disuse outside of people who learned it in its heyday and haven’t moved on, and irrelevance outside of legacy systems. It might not be quite as much a dead language as Latin (which also still exists and sees some use) but it’s well on its way there.




  • It’s too early to tell.

    Rust has a killer feature and a tonne of buzz, but poor ergonomics.

    Zig is developing into simple elegance and wonderful interop, but has more work to do before it will be widely usable.

    It’s entirely possible that ideas and lessons taken from them will inspire another language that ends up eclipsing them both.



  • I don’t remember the statement in the bug report verbatim, but it indicated that they intend to fix it, which is about what I had previously seen on other issues that they did subsequently fix. I expect it’s mainly a matter of prioritizing a long to-do list.

    I can’t think of a reason why it wouldn’t be possible. The protocol is continually evolving, after all, and they already moved message content to an encrypted channel that didn’t originally exist. Moving other events into it seems like a perfectly sensible next step in that direction.




  • There are a few that do a good job of protecting our messages with end-to-end encryption, but no single one fits all use cases beyond that, so we have to prioritize our needs.

    Signal is pretty okayish at meta-data protection (at the application level), but has a single point of failure/monitoring, requires linking a phone number to your account, can’t be self-hosted in any useful way, and is (practically speaking) bound to services run by privacy invaders like Google.

    Matrix is decentralized, self-hostable, anonymous, and has good multi-device support, but hasn’t yet moved certain meta-data into the encrypted channel.

    SimpleX makes it relatively easy to avoid revealing a single user ID to multiple contacts (queue IDs are user IDs despite the misleading marketing) and plans to implement multi-hop routing to protect meta-data better than Signal can (is this implemented yet?), but lacks multi-device support, lacks group calls, drops messages if they’re not retrieved within 3 weeks, and has an unclear future because it depends on venture capital to operate and to continue development.

    I use Matrix because it has the features that I and my contacts expect, and can route around system failures, attacks, and government interference. This means it will still operate even if political and financial landscapes change, so I can count on at least some of my social network remaining intact for a long time to come, rather than having to ask everyone to adopt a new messenger again at some point. For my use case, these things are more important than hiding which accounts are talking to each other, so it’s a tradeoff that makes sense for me. (Also, Matrix has acknowledged the meta-data problem and indicated that they want to fix it eventually.)

    Some people have different use cases, though. Notably, whistleblowers and journalists whose safety depends on hiding who they’re talking to should prioritize meta-data protection over things like multi-device support and long-term network resilience, and should avoid linking identifying info like a phone number to their account.