• 102 Posts
  • 768 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle

  • Probably the best and safest method is to look into the foam used for camera bags. That is the most common customisable option I know of that is practical. You’ll spend way less time and likely money if you cut foam to fit and pack everything.

    Obviously, I’m a fan of 3d printing. Heck I’m beside my printer that is chugging away at a design I made today. However. I think it is a matter of using the right tool at the right time. IMO, big drawer filling organizers are not ideal for printing. I can make wood cardboard or sheet metal boxes much faster and cheaper than printing.

    I could see myself designing a quick 2 rail holder with slots for each device to sit within, but that is going to be sloppy and likely wear poorly on the device. Best bet in my opinion is camera bag foam. If it is good enough for a half dozen $1k pro primes in a bag that gets banged around, it will work for some hand helds.


  • j4k3@lemmy.worldtoBuy it for Life@slrpnk.netFinding a BifL smartphone
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    2
    ·
    2 days ago

    All phones have orphaned kernels. They are orphans because the source code to run the physical hardware is not available. The manufacturer adds these binaries in the last step of the ROM. They cannot be reverse engineered effectively and every model is different. Reverse engineering one does nothing for the next.

    The hacked ROMs are maintained by people that know the kernel source at a crazy deep level. They know both the original kernel that the orphan is based on along with the state of every change and CVE that gets fixed in the current kernel. They are back porting all changes to the old kernel in order to keep it going. Eventually this becomes untenable or they lose interest.









  • The positives of a belt drive are maintenance, and that it stays clean so they are most popular with commuters that do not want a dirty pants leg or newbie chain tat. They are only common on heavier bikes like short haul commuters in general and require a “broken frame” that is designed for them in the first place. The lack of transmission gearing means you need to either know exactly what gear ratio you need and deal with only having one speed or you need an internally geared hub. All internally geared hubs have monstrous weight to add. So in practice, you do not find many of these on the market. Even with an e-bike, you still need a geared transmission unless you have throttle control without pedaling.

    On the other hand, for a hipster roadie, a fixie with a belt drive is some serious cred. Especially if they can dish it at the local group ride against people on flagship bikes.







  • Yeah, but it lacks the tree that tends to support more specialization. I still get on the EEVBlog forum from time to time but that kind of concentration of specialization is just not the default.

    To replicate that kind of ecosystem I think the platform would need a similar complex branching hierarchy and far more effective utility for searching. The element of time is too prioritized on a link aggregator like Lemmy. Community depth of specialization remains shallow because more intellectual engagement is slower and the mechanics of most recent comment engagement are not effective/implemented. Places like the EEVBlog often have the most engagement on very old threads that also concentrate a ton of history and useful information within the single thread. These threads are the primary anchor for the whole community. I think it would take some novel innovation to bridge a link aggregator’s ADHD with a forum’s depth and utility.


  • I’ve had this happen with AI stuff that runs in a Python venv. It only happens with apps that use multi threading, and usually when something is interrupted in an unintended or unaccounted for way. I usually see it when I start screwing with code stuff, but also from changing the softmax settings during generation or crashing other stuff while hacking around. There may be a bug of some kind, but I think it likely has more to do with killing the root threading process and leaving an abandoned child that doesn’t get handled by the kernel process scheduler in the standard way. If this happens I restart too.