4 ms·
> But here is a different, and I hope very provocative, reason that you should consider a terminal email client: > Local mail delivery does not traverse the In
by zokier 8y ago
> But here is a different, and I hope very provocative, reason that you should consider a terminal email client:
> Local mail delivery does not traverse the Internet, or any network.
The implication here being that you are running the clients on the email server. Wouldn't you effectively get the same security by tunneling IMAP over SSH?
- dsr_ 8y agoAny time you run the mail server and the clients connect directly to the mail server via encrypted paths (IMAP/S, SSH tunnel, VPN...) the Internet is not traversed, but the local network is.
- kbenson 8y ago> The implication here being that you are running the clients on the email server. That's a common scenario, but most linux/BSD distros ship with some mail server software installed and configured to run out of the box, even if also set to not allow external connections, as that's how the system delivers messages to users (e.g. cron output, etc). So almost every linux/BSD is a mail server, even if it may not be the mail server. If there's a main box that people in your company connect to as a terminal, email to local accounts on that box is essentially a internal messaging system. Hell, you could throw an IRC server on there with no outside access and use terminal IRC clients to have your own private chat channel as well. Who needs slack?
- digi_owl 8y agoUnix have all kinds of funny things if all happens within a single box. If you want to send someone a message, there is write (if the person have mesg set to yes). There is also talk, but it requires its own daemon. Seriously, _nix started out in the mainframe era. Meaning that the basic assumption was multiple terminals hooked up to a single computer, with a different user on each terminal. Sadly we have a generation or more that grew up with single user computers, and seems to insist on turning _nix into that rather than embrace what it can offer.
- canhascodez 8y agoMultiseat is a bit complex under X11, but certainly possible today. What do you see as the advantages of thin clients, though?
- kbenson 8y agoI think the point wasn't to specifically lament the lack of thin clients, but the lack of knowledge about how the systems are really designed be multi-user, and actually multi-concurrent-user, as opposed to systems like windows which eventually gained multi-user capabilities, and even then concurrent use isn't exactly the common case (and I'm not sure how well it works in practice, but I imagine with RDP it works well enough on the server products).
- canhascodez 8y agoAll of these tools and capabilities still exist; there's probably still some Unix beards hanging out on Nyx and SDF. Yet here we all are having a discussion on HN instead.
- kbenson 8y ago> All of these tools and capabilities still exist Yes... that's the point of the discussion. They exist, but there is (or is perceived to be) lack of knowledge about their existence and how to make use of them from some newer users, either because of the push for desktop linux, or for whatever reason. > Yet here we all are having a discussion on HN instead. I have no idea what you're trying to imply here. I suspect maybe we are discussing similar, but ultimately different, things.
- canhascodez 8y agoI'm implying that multi-user systems were supplanted by web applications, because multi-user systems did not offer good value, and do not scale. Neither do I see these systems being advanced in this thread based on their utility.