Using fish to work remotely

The real advantage to the fish protocol, as I stated in the introduction, is the ability to work remotely. Not that you wouldn't be able to do it without fish, but you remove a couple of steps that you'd have to take in order to keep files in sync. Ftp is ultimately a security risk and scp/sftp, though secure, means extra steps. With fish, you can create a file and edit it as if it were sitting on the same machine. The only thing you need to do is type a password. This is how we can create a file, for example:

Then, you'd simple choose your favorite text editor and start writing in your file.

When you're finished, just save your changes as you normally would. If it's a plain text file, you're changes are automagically sent over to the remote machine.

This system works out great if you're a programmer. Most source code is in plain text and so the ease of this system for developers is obvious. My text editor of choice for development is Emacs, and as you can see, Emacs is one of the choices on konqueror's menu. The only difference is that Konqueror will prompt you to authorize the changes, as it isn't in the suite of KDE applications.

Now what if you're going to use fish to edit other types of files? There's where you may run into some limitations, but they are easily overcome.