• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2025

help-circle




  • Yeah, I’m pretty sure the vast majority of those “no AI” forks will die very quickly. I mean, what is even the best case scenario? The fork is on life support with some bug fixes maybe? Because I do not believe it will get more development than upstream. Besides, upstream developers will be able to take any new development they want from the “no AI” fork but obviously not the other way around.

    I’m not an AI-bro but I think it’s completely unrealistic to expect you will be able to avoid software developed with AI assistance nowadays and even moreso in the future.


  • I regularly spend more than 8 hours a day at a keyboard but hand fatigue is not something I experience at all. Back, neck - sometimes. Hands? Never. Though I have put a lot of thought into ergonomics - desk, chair, staggered layout custom split keyboard, nice mouse (not vertical yet but I’ll probably switch soon). May I suggest you explore ergonomic equipment if you’re not familiar with it?

    Back when I tried playing guitar a bit I actually liked taking short breaks from work to play. It gave me something else to focus and come back to a problem with fresher mind.





  • I would say if you need to ask this, you might not be ready to expose your home sever to the internet. Please be VERY careful about this.

    With that being said, setting up reverse proxy (nginx) on the VPS should not affect the reverse proxy on your home server in any way.

    In the proposed setup, the VPS will be directly exposed to the internet - it’s the “gateway” to your network. If someone gains access to the VPS, they have access to your home server and probably other devices in your network. So yes, you need to secure the VPS as much as you can. Fail2ban or Crowdsec are a good idea. Setting them up on the home server wouldn’t really do anything against an attacker with access to the VPS.