• 0 Posts
  • 620 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • The feature itself is great. It records the last two hours by default and lets you easily create clips from that. The editor is right there in the Steam overlay, it’s pretty great.

    I only used it under Linux, and that’s where I’d say it is still very much a beta experience. I have an AMD Radeon 7800 XT. Most of the time, Steam picks up on its hardware acceleration - sometimes it doesn’t. When it doesn’t, it falls back to CPU encoding (obviously) which occupies around 3-4 cores on my 7950X3D to record 3440x1440 at the highest quality setting. GPU encodes are H.264 even though the GPU is perfectly capable of encoding AV1. Performance impact ranges from almost zero to as much as 30%, which seems a bit excessive. On some games that have a splash screen (Sea of Thieves for example), all it will record is said splash screen, even when it’s not shown anymore: you get gameplay sounds, but the video is just a static image with mouse cursor artifacts. It didn’t record sound from one of the microphones I tried. After swapping it out for a different one, my voice is being recorded. At least one session the shortcut for saving a clip just resulted in an error sound instead of a clip being saved.

    So it’s a bit disappointing so far. Yeah, Linux shenanigans and relatively small user base, but Valve out of all companies should treat Linux as a first-class platform. Yes, they do a lot for Linux, with Proton and whatnot. But ironically Steam itself is only in an “okay, it kind of works” state. No official packages for anything but apt-based distributions and Wayland (scaling) support is meh at best.

    It did seem to work a lot better on the Steam Deck with very little performance impact in my short testing, so there’s that.






  • The main thing (by far) degrading a battery is charging cycles. After 7 years with say 1,500 cycles most batteries will have degraded far beyond “80%” (which is always just an estimate from the electronics anyway). Yes, you can help it a bit by limiting charging rate, heat and limit the min/max %, but it’s not going to be a night and day difference. After 7 years with daily use, you’re going to want to swap the battery, if not for capacity reduction then for safety issues.


  • I think I have a simple function in my .zshrc file that updates flatpaks and runs dnf or zypper depending on what the system uses. This file is synced between machines as part of my dotfiles sync so I don’t have to install anything separate. The interface of most package managers is stable, so I didn’t have to touch the function.

    This way I don’t have to deal with a package that’s on a different version in different software repositories (depending on distribution) or manually install and update it.

    But that’s just me, I tend to keep it as simple as possible for maximum portability. I also avoid having too many abstraction layers.



  • Technically, wired charging degrades the battery less than wireless charging, mainly because of the excessive heat generated by the latter. The same way slower wired charging generates less heat. Lower and upper charging limits also help (the tighter the better).

    But I personally don’t bother with it. In my experience, battery degradation and longevity mostly comes down to the “battery lottery”, comparable to the “silicon lottery” where some CPUs overclock/undervolt better than others. I’ve had phone batteries mostly charged with a slow wired charger degrade earlier and more compared to almost exclusively wireless charging others. No battery is an exact verbatim copy of another one. Heck, I had a 2 month old battery die on me after just ~20 cycles once. It happens.

    Sure, on average you might get a bit more life out of your batteries, but in my opinion it’s not worth it.

    The way I see it with charging limits is that sure, your battery might degrade 5% more over the span of 2 years when always charging it to 100% (all numbers here are just wild estimates and, again, depend on your individual battery). But when you limit charging to 80% for example, you get 20% less capacity from the get go. Unless of course you know exactly on what days you need 100% charge and plan your charging ahead of time that way.

    Something I personally could never be bothered with. I want to use my device without having to think about it. If that means having to swap out the battery one year earlier, then so be it.










  • narc0tic_bird@lemm.eetoPrivacy@lemmy.mlKagi search engine working with Russia
    link
    fedilink
    arrow-up
    116
    arrow-down
    4
    ·
    edit-2
    19 days ago

    I expected something more shocking when I read “working with Russia”.

    Kagi uses multiple search backends, and of course it needs to forward search terms to these backends. These backends probably can’t trace the searches back to the individual Kagi user though, but Yandex could still analyze search trends for example.

    What’s worse is that - unless they use Yandex’ API for free - customers indirectly (and likely unknowingly) support a Russian company with their paid Kagi subscription.

    Kagi should at the very least release a statement about this claim.