ed25519 verify key: 6614c7acfe8e7419bbc26709d7f0fdcc55d8258f205a95173ce37e42e1715462

  • 0 Posts
  • 41 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle








  • It’s probably a bit dangerous to expose your internal network in this way. If you really want a server running at home, there are interesting services which provide that for a fee, or you could set up a “reverse ssh proxy”.

    It’s easier to do on some flavor of Linux, but you will set up a background service to ssh to a cloud server you rent, which links a local port on the cloud server to a local port on your home computer. You can then run a web service like caddy server on the cloud server to securely serve this port.

    I realize this sounds rather complex, but something to look into and learn.

    Your Caddyfile on the cloud server will look something like this:

    my_subdomain.my_domain.com {
        reverse_proxy / {
            to 127.0.0.1:8081
        }
        encode gzip
    }
    

    And the service on your local will look something like this:

    [Unit]
    Description=Keeps a reverse tunnel to '<your cloud server ip>' open on port 8081 on the remote server
    After=network-online.target
    
    [Service]
    Environment="AUTOSSH_GATETIME=0"
    ExecStart=/usr/bin/autossh -N -M 10986 -o "PubKeyAuthentication=yes" -o "PasswordAuthentication=no" -o "ExitOnForwardFailure=yes" -R 8081:127.0.0.1:8080 root@<your cloud server ip> -i <path to your ssh key> -p 2097
    
    ExecStop=/bin/kill $MAINPID
    Restart=always
    RestartSec=5
    
    [Install]
    WantedBy=multi-user.target
    

    You will have to allow ssh on a non standard port (arbitrarily 2097 here), that way you can still use ssh on the standard port 22. I have some services running like this through a NAT for years.




  • Weekend of Sept 8-9 2001, went to a house party in long island NY with some friends from our then-town in upstate NY. Friends mom, our ride, ended up on a crack binge and the party house started getting, uhh sketchy. So four of us got out of there on foot walking down train tracks, pooled funds for a train to at least get back to NYC try to hop our train back up north somehow.

    This was middle of the night Sunday the 9th, and we headed to the old liberty park after my friend in area didn’t answer his door. Slept in the park one block from WTC and had my brother upstate wire us money for the train, which we took after WALKING from wall street to grand central (no money). We got back upstate Sept 10, and the following morning 9/11 happened. My friend and I were the type to have been helping people get out of the buildings, he is a firefighter now, one of the others is a nurse.







  • I did one where I went through a few rounds of interviews, technical and otherwise. In talking with the developers, they mentioned that they were trying to integrate a certain client side framework into their backend frameworks build process, without success. Get to the final stages, and the director of engineering asks me to work on this take home project to, you guessed in, integrate the js framework into the build process of the backend framework.

    I sent them a strongly worded rejection email. It was a realreal eye opening experience.


  • Ridiculous take home tests are probably the number one reason I decline to continue interview processes. If you think that building a client, an API, wiring it up to some other third party API, then deploying is a reasonable scope for an unpaid interview challenge then you are very bad at scoping software projects and the most important thing I can do for you is tell you as much.

    I told one start up if I built what they asked for in the interview, I would pursue funding from their investors and launch it as a competitor- it was that similar to what their actual app did.