• 0 Posts
  • 92 Comments
Joined 2 years ago
cake
Cake day: March 3rd, 2024

help-circle
  • it’s one of those cases where if you have to ask, you should probably just use systemd. anything else is outdated or a passion project based on some idealism, which i’m all for, but if you’re worried about gaming performance as a primary concern i’d put it out of your mind. for example, i’m an obsessive tinkerer that uses NixOS and Arch before that and i use nushell and Neovim and Hyprland, but i use systemd cuz i don’t see a reason not to. it’s well supported and stable.


  • i’ve been a big fan of Jujutsu (jj) since adopting it a few weeks ago. things i used to avoid with git like proper rebasing and focused commits become so much easier, in addition to the benefits of conflicts being easier to handle. the learning curve i thought was going to be grueling only took a couple days to get used to, and honestly interop with GitHub and my team’s particular workflow were the hard parts. so not only is it useful, powerful, and becoming more important to my workflow all the time, it’s a joy to use compared to git.

    i guess honorable mention to zoxide, which has basically replaced cd for me since it does everything cd does but also keeps a small db of your most commonly visited directories so you can just do z Downloads or z my_project or whatever from any directory


  • “unhackable” is a bit sensationalized here. the Xbox One is actually a security success story not because it is impossible to hack, but because it’s a rare example of a console that wasn’t hacked in its service lifetime. at the risk of giving praise to Microsoft, the architecture is actually really neat and informed the security features of subsequent Windows releases, ie a hypervisor with sandboxed sub containers (this is why they required TPMs).

    (also i’m not agreeing with requiring a TPM for general purpose machines; they make sense on a bespoke hardware platform like a game console)

    i bet this hack is nuts, but the blue team deserves some level of kudos

    https://youtu.be/U7VwtOrwceo






  • chrash0@lemmy.worldtoTechnology@lemmy.worldThe EU Moves To Kill Infinite Scrolling
    link
    fedilink
    English
    arrow-up
    61
    arrow-down
    3
    ·
    edit-2
    2 months ago

    i personally have pushed back on every “infinite scrolling” feature request from product designers. first, you think you need it; you don’t. second, you think it’s just so nifty! it isn’t. oh is your content is dynamically generated? what was wrong with Reddit’s pager that launched that site into popularity?

    it’s unnecessary complexity that hides information from the user, makes API calls (which are, spoilers, paginated) more complicated, can cause the obvious memory/resource consumption issues, and just generally disempowers the user. which i guess on a social media app is the point. but totally counter to the goals of a fleet management system lol


  • someone was asking for a GUI, so not going to be an ffmpeg expert. likely the LLM would recommend ffmpeg anyway. plus you would run YOLO (or maybe CLIP) locally; it has been running on Android phones since 2020 at least. a Jupyter notebook would also give a quick and dirty GUI to visualize and document the solution. plus “motion detection” is probably not the full story, and any video will probably have artifacting that means you’d have to tune the motion detection algorithm or end up with a bunch of garbage artifacts/false positives in the end. also, sounds like the user isn’t looking for something long-running like Frigate. if the user isn’t familiar with Python and wants to do something downstream like sort the outputs or whatever, an LLM would help with that.

    sure, programmatically, it’s not a difficult problem, but like it or not it can be solved by someone without an advanced CS degree with an LLM precisely because the problem is easy. no easily ready solution exists, but that doesn’t mean it can’t be done. “just use ffmpeg” to someone like my dad who might have the know how to install Linux but isn’t a programmer isn’t exactly the simple advice it sounds like.









  • i think it’s easy to make comments like this from the peanut gallery, with the benefit of hindsight and a self-selected group of users who will agree. but Apple should be legally obligated to address this. the solution can’t be “this idiot didn’t spend his nights and weekends doing 3-tier backups and high availability infrastructure diversity!”; that’s not scalable. if we just accept that companies can do this, they will continue to. but this has been on the front page of HackerNews. it’ll probably make it to Tim Apple’s desk eventually, so we’ll see what shakes out.




  • honestly, where NixOS shines for me is in my homelab. i don’t always have time to fully document what i’m doing, but my NixOS config is code-as-documentation for when work burns all of my memories away and has a git log and conflict management so i can manage multiple systems that share common config.

    and once you find out you can have services run on systemd with syntax like services.jellyfin.enabled = true you’ll never want to go back to containers, although it has ways to manage those as well.

    it’s overall a great OS for tinkering and deploying small services across small networks. not sure how it scales, but for my use case it’s damn near perfect