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 .

“like netcat” huh, i wonder what netcat is…

“netcat (often abbreviated to nc) is a computer networking utility for reading from and writing to network connections using TCP or UDP. The command is designed to be a dependable back-end that can be used directly or easily driven by other programs and scripts. At the same time, it is a feature-rich network debugging and investigation tool, since it can produce almost any kind of connection its user could need and has a number of built-in capabilities.”

it’s the future, just like blockchain and NFTs. I mean really if you don’t marry an LLM right now (ignore the gun i’m holding to your head, don’t change the topic) you’ll just go mad at some point as everyone else leaves you behind…

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.

the problem with “just a tool” is that using it will inherently change how you act.
Best concise way i can put it is that it’s like how better hardware has largely just resulted in software not really caring about efficiency any longer.

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.

i’m so curious what the argument against banning AI slop would even be, lmao

i maintain that the most sensible thing would be to develop a minimal linux “shim” that just runs an android VM, then you no longer have to develop ROMs for every specific device and you can start slowly porting features over to the linux side of the whole shebang.