Strangely no reference to "the most underrated configuration file" aka .ssh/config (reference is some internal docs I wrote) where you can name hosts whatever you want, define jumphosts to reuse to connect to different servers, specify different private keys and usernames for each host, and transform a monstrosity like
One other super-interesting feature is connection multiplexing and keeping connection alive with the ControlMaster and ControlPath directives in your ~/.ssh/config file.
The nice thing is that it makes opening a new ssh connection much faster, which if you make a lot of connections, it can be very handy.
Note that it has one pitfall that is hard to notice: if you a use per-invocation `-o SendEnv`, that gets ignored in favor of the background ssh persistent connection that is keeping the session up. In other words, your connection bear the `SendEnv` of that initial connection and not of the new ones you are creating. No warning is printed.
This is a really refreshing link in the HN feed, which is often dominated by the latest bloatware fashion trends (which includes most (almost all) chatbot applications).
One different preference of mine is to mount a remote directory via SSHFS instead of playing media via an sftp:// link.
I also prefer a clicky-clicky media player over MPV and have used VLC for many years.
Another feature of OpenSSH that facilitates this philosophy is port forwarding, both forward and reverse. This feature prevents having to open pretty much any other port in the firewall.
Its sad to see so many technically literate people still working under the feature poor yoke of windoze 8-( So many methods become instantly available when using a free unix system. Which also typically never require downloading binary executables from sketchy third party websites.
> I also prefer a clicky-clicky media player over MPV
Not sure what do you mean by that; if you compile mpv with lua support (in case your distro/whatever doesn't ship it that way, that is) you get a clicky-clicky little osd thing within the mpv window that suffices (back, forward, playback control, volume...)
Unless the guys on tech circles the TFA is mentioning are all singles and plan to stay so voluntarily or not, a (good?) portion of them have, had, or will have 3 year olds!
In fact I maintain one of those setups mentioned by TFA with some neighbours (lots of tech people/artists with rare media in the neighborhood for reasons), and friends and family in other countries.
The whole point of most of these setups (for people with family), is to be safe, simple, efficient, and low-maintenance for the whole family to be able to enjoy media.
Strangely no reference to "the most underrated configuration file" aka .ssh/config (reference is some internal docs I wrote) where you can name hosts whatever you want, define jumphosts to reuse to connect to different servers, specify different private keys and usernames for each host, and transform a monstrosity like
ssh -i ~/.ssh/key_A -o ProxyCommand="ssh -i /very/very/long/directory_name/hidden_somewhere/key_B user_B@jumphost -W %h:%p" user_A@192.168.1.5
into
ssh myserver
And how many knows windoze ships an ssh client (that yes supports .ssh/config) since years?
One other super-interesting feature is connection multiplexing and keeping connection alive with the ControlMaster and ControlPath directives in your ~/.ssh/config file.
The nice thing is that it makes opening a new ssh connection much faster, which if you make a lot of connections, it can be very handy.
See https://ldpreload.com/blog/ssh-control for some examples
Note that it has one pitfall that is hard to notice: if you a use per-invocation `-o SendEnv`, that gets ignored in favor of the background ssh persistent connection that is keeping the session up. In other words, your connection bear the `SendEnv` of that initial connection and not of the new ones you are creating. No warning is printed.
This is a really refreshing link in the HN feed, which is often dominated by the latest bloatware fashion trends (which includes most (almost all) chatbot applications).
One different preference of mine is to mount a remote directory via SSHFS instead of playing media via an sftp:// link.
I also prefer a clicky-clicky media player over MPV and have used VLC for many years.
Another feature of OpenSSH that facilitates this philosophy is port forwarding, both forward and reverse. This feature prevents having to open pretty much any other port in the firewall.
Its sad to see so many technically literate people still working under the feature poor yoke of windoze 8-( So many methods become instantly available when using a free unix system. Which also typically never require downloading binary executables from sketchy third party websites.
+1 for "all you need is SSH"
> I also prefer a clicky-clicky media player over MPV
Not sure what do you mean by that; if you compile mpv with lua support (in case your distro/whatever doesn't ship it that way, that is) you get a clicky-clicky little osd thing within the mpv window that suffices (back, forward, playback control, volume...)
This is great and... On a small scale, you don't even need samba or nfs.
Many file browsers can mount remote directories via sftp, and can browse the files as if it was a local directory.
Also: KDE and some GTK-based graphical environments have subsystems for this:
- https://en.wikipedia.org/wiki/KIO
- https://en.wikipedia.org/wiki/GIO_(software)
my 3 year old is not going to type
she can't type yet...Is your three year old in the tech circles TFA is referencing?
Unless the guys on tech circles the TFA is mentioning are all singles and plan to stay so voluntarily or not, a (good?) portion of them have, had, or will have 3 year olds!
In fact I maintain one of those setups mentioned by TFA with some neighbours (lots of tech people/artists with rare media in the neighborhood for reasons), and friends and family in other countries.
The whole point of most of these setups (for people with family), is to be safe, simple, efficient, and low-maintenance for the whole family to be able to enjoy media.