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

help-circle

  • yeah no sorry, you don’t just get to conveniently ignore all the systematic problems with AI usage.

    AI datacentres are displacing people, deforesting huges swathes of land, placing massive loads on electrical grids which makes electricity more expensive and encourages more fossil fuel usage, using shitloads of water for cooling; and AI is replacing workers, sneakily influencing users, and people offloading cognitive effort onto it results in their skills atrophying and code becoming unmaintainable.

    Using AI to write code is like always buying fast food: it’s bad for you, bad for the environment, fucking expensive, and means you never learn how to actually cook your own food.







  • the thing with openwrt is that you have the freedom to fuck it up, which is exactly what tends to happen to people who know enough to come up with the idea of installing a different OS on their router.
    So you really should make sure that you’ll be able to deal with it when you eventually fuck something up because you wanted to configure the blinking pattern of the LEDs or whatever.

    Though to be fair openwrt makes it fairly easy to back up configurations and just reinstall everything from scratch





  • 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 .
    





  • Swedneck@discuss.tchncs.detoOpen Source@lemmy.ml•Ban AI Slop?
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    2 months ago

    that comparison works quite well to explain why i think it can’t legally qualify as open source, too!
    Both ai-generated software and short generic scripts aren’t really unique in any meaningful way, there’s no creativity in it and therefore it really shouldn’t be considered covered by copyright in the first place.



  • Swedneck@discuss.tchncs.detoOpen Source@lemmy.ml•Ban AI Slop?
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    2 months ago

    what makes you think it would become an unused backwater? The people most vocally anti-AI are also those most likely to actually engage with places like this. And there’s plenty of people here who support banning AI slop on the community so clearly there’d still be people left after you leave.