I do a little bit of everything. Programming, computer systems hardware, networking, writing, traditional art, digital art (not AI), music production, whittling, 3d modeling and printing, cooking and baking, camping and hiking, knitting and sewing, and target shooting. There is probably more.

  • 14 Posts
  • 405 Comments
Joined 3 years ago
cake
Cake day: June 4th, 2023

help-circle





  • Like others said, you did fine. Make yourself safe, report it, call security if required, but also understand that when people are under extreme duress such as the death of a loved one, they want to blame anyone and anything.

    People have a really hard time coping with the fact that people often die without reason, unceremoniously, to such a degree that they feel they have been wronged by something or someone, even if there isn’t anything to blame.

    When this happens they may pick something they perceive as being in proximity to the event to blame to try to make sense of it. It might be disease, the equipment, the medication, a family member, or in this case yourself.

    You deal with this by knowing the facts of what happened, and knowing you did your best and aren’t to blame, and by understanding that people lash out when they are upset.

    Nothing you could have said would have helped the situation with this person in their state, so saying nothing and leaving to de-escalate the situation is 100% the best thing you could have done.



  • 1 - Ask them if they can either not drop the weights, or if the time this occurs can be adjusted to make it less of a problem. Document that you asked them somehow including date, time, what was said in the request, and how the request was sent.

    2 - If nothing can be fixed through step 1 review your condo rules and verify if they are breaching them by doing what they are doing, see what fines are like for each breach of whatever rules is covered by this. If there are no rules for this, you are basically screwed and should either lobby your condo board/property manager for a change in rules or move.

    3 - Set up a camera/mic and have your phone handy. Record the noise when it happens noting the date and time.

    4 - Submit a complaint to the condo board/property manager every time this happens including the date and time and the recorded evidence, citing which rules are being broken. Be prepared when you start doing this that your neighbor might try to retaliate. If they retaliate by making the noise worse, do the same thing recording it and sending it up the line. If you play music really loud or whatever, they may also try to retaliate by submitting complaints about you - try to not let them catch you out on that.

    Eventually, if your property management/condo rules are set up in a reasonable way they would either stop, get evicted by their landlord who is now receiving fines, or be evicted by proxy because the fines are too numerous and expensive. Repeatedly making complaints to your board/property manager usually gets them involved pretty quickly because it creates a constant nuisance they can’t easily ignore.



  • If you don’t need stuff publicly accessible, and just need it accessible to you, then set up a small computer on the network as an ssh Bastion host/jump server, put it on a VPN connection with a VPN provider that offers dyndns, forward the ssh port through the dyndns, and then off network, reverse proxy in with socks5 via key based ssh -D to gain access to all the services available inside the LAN.

    Been doing this for a few years, works great and no one is getting in without my ssh key.



  • I feel similarly especially about remmina, though as I understand it this is not necessarily the fault of Wayland but of the various applications and drivers not offering or having been developed to support wayland yet (I’m quite sure this is the case of Remmina anyway).

    It’s too bad because on Debian 13 here wayland actually speeds up the general interface for me - if it weren’t for these shortcomings in-app then I would be running it for sure.

    I would hope plasma’s decision pushes the application developers to catch up a bit.


  • I’m a professional. I expect to be treated like one. If there are companies who are serious about hiring a professional, I’m all in. Please engage me.

    That’s really well said.

    I remember being in the same situation a couple years ago in which I was accepted to an interview through a video chat web application hosted by the company.

    To my horror, when I joined the meeting, it was not a video chat interview. It was a series of recorded clips of their HR person reading off questions, the clips pausing, and then a timer showing up on the screen noting “You have 15 seconds to answer”.

    I was so put off by this that after the first question, I decided to spend the rest of the time I was being recorded explaining to them under no uncertainties that this was one of the most unprofessional interview processes I had ever engaged in, and that they had made it clear that they did not value my time whatsoever, so I had no reason to reciprocate.








  • Like others said, the bottle neck will be the OS doing it’s thing with python rather than the hardware. Remember that you can perform pulse width modulation with the GPIO, so they can physically toggle states really very fast.

    I seem to recall that there is a GPIO header file for C available for the pi somewhere. If python proves too slow for what you want to do, you could look into writing something in C instead to try to speed things up potentially.