• 14 Posts
  • 1.02K Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle






  • I’ll never drink again, but there are some days still that I wish my mind could be as numb as it was while I was a raging alcoholic. That thought is usually replaced with remembering how shitty I always felt and how I didn’t give a fuck about anything. Life was a blur.

    A mostly clear mind and recovering body is a very good thing. Daily stress is easily managed with regular exercise and chronic anxiety and depression is only a tiny fraction of what it once was. It’s a good life now.

    I believe the lifestyle changes not only lengthened my life, but it also stretched out my perceived time as well.




  • I would tweak that a hair and tell people just to make an account somewhere and observe for a bit. Lemmy can have some very distinct groups that reside on very specific instances. Or not. It’s a “pick your adventure” kind of scenario, IMHO.

    It took about six months or so for me to settle into .ca after bouncing around a bit. It’s not really a pain to switch instances, but I personally like my chat history in one spot and I like the concept of a ‘home instance’.

    Depending on your client and your settings, your feed could have a bias that leans in the direction of the posts on your home instance, so that is something of note. Not saying that is bad or good, it just is what it is.



  • When I use it, I use it to create single functions that have known inputs and outputs.

    If absolutely needed, I use it to refactor old shitty scripts that need to look better and be used by someone else.

    I always do a line-by-line analysis of what the AI is suggesting.

    Any time I have leveraged AI to build out a full script with all desired functions all at once, I end up deleting most of the generated code. Context and “reasoning” can actually ruin the result I am trying to achieve. (Some models just love to add command line switch handling for no reason. That can fundamental change how an app is structured and not always desired.)





  • I agree with the comments on this forum (https://www.thehighroad.org/index.php?threads/mushrooming-22-lr-case-heritage-rough-rider.891807/) that the cylinder could have a machining defect. (Basically a headspace issue, also but kinda not. The cartridges are sitting too deep in the cylinder itself.)

    If there is room for the brass to get pushed back far enough for it to mushroom out, something is seriously wrong. The issue could manifest from a machining error as small as 5-10 thou, I am speculating.

    My first thought was excessive chamber pressure, but the bulging would be much worse around and behind the rim itself if that were the case.

    The bullet and the brass get pushed in opposite directions and if the brass can move, it will move before it deforms. If it deforms, it’ll deform at the weakest spot first, like we see in your pic. (Excessive chamber pressure tends to expand the brass and lock it in place. With center-fire, it’ll blow the primers out or have a hole punched in them from the firing pin first. With rim fire, the pressure pushes back on the rim.)

    Also, check for excessive slop with the cylinder. If it can move forwards and backwards too much, that could also telling of issues with other parts of the gun. (Like I mentioned before, it doesn’t take much for a gun to be out of spec enough to cause issues with brass.)




  • Apps are somewhat buggy right now. My shokz will partially disconnect after the first song and exercise audibles are non-existent. (The audio mutes, but the watch still responds to play/pause button presses. This could be just an issue with the shokz app being confused for the time being.)

    No difference in GPS connect time from the pixel watch 3, which has been historically buggy at times.

    But yeah, random glitches all over the place. It’s tolerable enough and would expect app updates to fix most of them.


  • I gave this some thought and I still can’t decide what is the best option.

    From one perspective, not binding the bundle to the spine follows a clean horizontal/vertical layout and isn’t tightly bound to the movement of the spine. This may be “shortest path” and save on cable cost. However, there could be conditions that would stretch the cable if it were only tied to the neck and hips.

    If the bundle was tied closely to the spine, the cable would be stretched less when the spine moves, but it would be moving and bending more. Cable cost could be a bit more as the total path is longer.

    Installing something similar to a cable chain on the spine to let the bundle float (while still being contained) is probably a decent meet-in-the-middle solution between the above two options.

    (In hindsight, me giving this any serious thought was bizarre.)