For anything important, use matrix instead of lemmy DMs.

  • 0 Posts
  • 192 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle



  • Warrantied drives still fail, they just happen to ship you a replacement.

    Commercial drive trashing solutions are basically a smaller, fancier version of the mechanism in a log splitter.
    You could probably rig a sketchy drive wedge/bending thing with a pump jack rather easily.
    Wear PPE.

    The odds of someone taking a failed drive and transplanting the platters to a working drive is pretty low to begin with.

    Me? I don’t have tons of drives to destroy, so I just unscrew the thing, get the platters out and smash those.






  • So, the SD Association is absolutely fucking insane when it comes to giving labels to literally anything.

    The Steam Deck supports UHS-1 microSD cards.
    That’s the name of the bus. There’salso UHS-2 and UHS-3, but they’re backwards compatible with UHS-1, so that’s whatever.

    Speeds…
    Some cards used speed “classes”, like Class 10…
    There’s also U1 or U3 speeds (which is a speed rating independent of the bus. (A U3 cards is probably a UHS-1 card.
    Some have a speed rated with a V, like V10, V30, etc.
    They often have multiple labels too.
    These can all be used to label the speed of a UHS-1 card:
    UHS Speed Class

    • U1: 10 MB/s minimum write speed.
    • U3: 30 MB/s minimum write speed.

    Video Speed Class

    • V6: 6 MB/s minimum write speed.
    • V10: 10 MB/s minimum write speed.
    • V30: 30 MB/s minimum write speed.
    • V60: 60 MB/s minimum write speed.
    • V90: 90 MB/s minimum write speed.

    Class 10

    • Class 10: 10 MB/s minimum write speed (legacy).

    Anyway, U3 is basically the same as a V30.
    U3/V30 would be the minimum I’d get for the Deck. Price being the deciding factor for the rest.
    I don’t really care if the card ever fails, so brand was (mostly) irrelevant in my choice.





  • I get what you mean and yea I don’t think you can easily use groups for that.
    Zones have a several things going on.
    In no particular order:

    1. A zone’s state is the number of people in it.
    2. Zones can be used as enter/leave triggers in automations.
    3. A person’s state becomes the name of the zone when they’re in them.

    Making a mock entity for #1 is easy enough, a helper number thing whose state is the sum of the group members’ states.
    The other stuff is more complicated.
    #2… Might be easier to add the different zones as multiple triggers, which might be a pain to manage. But then, I assume you’d also want to ignore whenever someone moves between zones in that same group.
    #3… idk, if it’s just for displaying purposes in that person’s “badge” thing, just use the same display name for all zones in group. If it’s for use in an automation, then you probably need to duplicate everything again.

    Might be easier to implement polygonal zones than group normal ones.

    I think nodered might already have that geofencing feature.

    There’s a bit of discussion in here: https://github.com/home-assistant/architecture/discussions/1014


  • Depends on the game a lot.
    Sometimes it’s just ABXY buttons where I don’t wanna move my thumb off the right joystick.
    Sometimes, one paddle activates a layer shift to have more mappings.
    Like if a game has more controls than you could fit, layers can help extend the possibilities and paddles area decent way of activating them.
    If a game is heavy on QTEs, like spam X really fast to do something, I might just map a paddle to enable a layer shift that turbo spams the other button.


  • Yea, it’s not the first time I’ve seen this discussion either.
    I don’t wanna seem like I’m not believing you or belittling your experience, I just find it weird that we (we, users, as a whole, not just you and I) have such wildly different experiences with it.

    As is, I have a vastly better experience with my own nextcloud than with corporate’s onedrive, with more stuff on mine.

    Wish I knew why it’s so inconsistent.
    Even though my nextcloud experience is fine, I know plenty of people with the opposite.


  • Legit have had none of these issues.
    I do get a notification once in a while if I modify a picture fast enough, like a quick crop and it’s still uploading. Like snap pic and edit within the same 5 seconds or so.
    Basically just a: “there are multiple versions of the same file (which is true), which one do you wanna keep”.

    Then again mine is running on a pretty beefy server which might hide issues rooted in performance.
    I remember it being hell when I was running it on a RPi.