• 0 Posts
  • 161 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle


  • y’know this actually made me think of a good plot for a short spinoff:

    Hardcore christian person finds the death note, spends some time researching who the most evil people are, then follows a year of writing one name every day after which they go through a ritual and prayers and then repeat the next day, and at the end they finish by writing their own name because they know humans can’t be trusted with that power and consider themselves to have simply been the hand of god and now it’s time to face His judgement.

    Basically just literally Silas (the white haired dude) in the Da Vinci Code.


  • i mean they’ve already shown that you can just straight up have an image model generate the game in real-time without even writing code

    the future is the reverse matrix: all-but-sapient computers forced to dream our games
    I miss when computers were fancy rocks we tricked into doing maths…












  • And this can presumably hopefully finally fucking condemn hamachi to the grave, maybe?


    Forward local ports to a tailcat server

    To make ports served by a tailcat server available as ordinary local TCP ports (for browsers, database clients, or other tools that do not support SOCKS or stdio), run forward with the server’s tailcat address:

    $ tailcat serve 8080,3306
    # 🐈 Server listening with new address: tcXXXXXXXXX
    
    $ tailcat forward tcXXXXXXXXX 18080:8080 3306
    

    A local port of 0 asks the operating system for a free port; each listener prints its address once it’s listening.

    To forward local ports to assets on the network reachable by an exit-node server, run the server in exit-node mode and specify each remote IP address and port in the mapping:

    $ tailcat serve exit-node
    # 🐈 Server listening with new address: tcXXXXXXXXX
    
    $ tailcat forward tcXXXXXXXXX \
        3001:172.23.52.30:3001 \
        17170:172.23.52.31:17170
    

    This forwards 127.0.0.1:3001 to 172.23.52.30:3001 and 127.0.0.1:17170 to 172.23.52.31:17170 through the exit-node server.

    By default, listeners bind to 127.0.0.1 and diagnostic logs are suppressed. Pass --verbose before the subcommand to enable verbose networking logs. Use --bind=0.0.0.0 only when clients on other machines should be able to connect:

    $ tailcat forward --bind=0.0.0.0 tcXXXXXXXXX 18080:8080
    

    Press Ctrl-C to stop forwarding.


  • Okay so i think this section is one of the most useful ones for a normal user:


    Send and receive files

    To receive files, run a drop box and share the printed tailcat address:

    $ tailcat recv ~/inbox
    # 🐈 Server listening with new address: tcXXXXXXXXX
    

    The sender then runs:

    $ tailcat cp report.pdf tcXXXXXXXXX:
    

    tailcat cp runs the system scp with the connection routed through tailcat, so you get its usual progress display, and -r for directory trees. The drop box is write-only: senders can’t list the directory, read anything back, or touch existing files.

    To offer files instead, serve a directory read-only (the default) or read-write:

    $ tailcat serve files                  # current directory, read-only
    $ tailcat serve --files=/pub:rw files  # a given directory, read-write
    
    $ tailcat ls -l tcXXXXXXXXX
    $ tailcat cp tcXXXXXXXXX:report.pdf .