21–30 of 95 posts
I think there's a version of elinks (or one of the other text based browsers) that can display images if you are running on a framebuffer console
There's a solution to that though: running Firefox in the terminal with brow.sh [1]
/me procedes to launch "youtube-dl -f22 https://www.youtube.com/watch?v=0-2Ja7T9YF8"
https://neomutt.org/ The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal. It actually makes a lot of sense as an email client and is surprisingly ergonomic. I also enjoy the fact that my config is a normal dotfile that I can version control etc. Also, your passwords can be encrypted using the tools that you choose, as opposed to whatever home grown crypto (if any) the [insert random Electr…
Mutt/Neomutt is great once you got over the initial trauma of the keybinds and configuring the config plus theme. Except when it comes to HTML e-mail which is a lot more common that I'd like it to be. For a more up-to-date guide on how to use GPG for your e-mail password [1] [1] https://pthree.org/2012/01/07/encrypted-mutt-imap-smtp-passw...
https://neomutt.org/ The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal. It actually makes a lot of sense as an email client and is surprisingly ergonomic. I also enjoy the fact that my config is a normal dotfile that I can version control etc. Also, your passwords can be encrypted using the tools that you choose, as opposed to whatever home grown crypto (if any) the [insert random Electr…
Mutt/Neomutt is great once you got over the initial trauma of the keybinds and configuring the config plus theme. Except when it comes to HTML e-mail which is a lot more common that I'd like it to be. For a more up-to-date guide on how to use GPG for your e-mail password [1] [1] https://pthree.org/2012/01/07/encrypted-mutt-imap-smtp-passw...
Earlier quoted context omitted.
If you call something (watching videos/pictures or browsing in a framebuffer) which has been working since the end of '90s "new" then you've grown old. A while ago, if I might add. And the ability to use a CLI on a large say 1280x1024 resolution was nice as well, given the dots per inches on CRTs in late 90s.
Some people would kill the lice first but sophisticated users preferred live ones which enabled advanced effects like 'dynamic text' and 'escape sequences'.
https://neomutt.org/ The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal. It actually makes a lot of sense as an email client and is surprisingly ergonomic. I also enjoy the fact that my config is a normal dotfile that I can version control etc. Also, your passwords can be encrypted using the tools that you choose, as opposed to whatever home grown crypto (if any) the [insert random Electr…
I personally use (al)pine and I could not agree more.
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.
So, for instance, when I send an email to one of my engineers at rsync.net, even though it is sent in plaintext, it is a private communication and cannot be intercepted by either an ISP or some global observer. It's nothing but a local file operation between two mailspools...
Further, it would be extremely difficult to phish someone who is viewing their email in the terminal. The effort that it takes to view and copy a URL is greater than the discernment required to identify it as suspicious - so you'll catch them every time.
Earlier quoted context omitted.
IMHO The 20+ years spent trying to make a desktop version of linux has SEVERELY reduced overall knowledge of unix practices and patterns. I'm not just talking about things like automake or the contents in /bin that younger programmers never learn, but the CLI in general. A while back I was working with an intern who as struggling with using distributed linux boxes because all he knew was Gnome: the CLI was utterly fo…
It is not a question of age, most of my older colleagues as an intern used desktop apps / GUI git clients and had few UNIX experience.
How old are your "older colleagues"? I'm 35 and I remember "the land before Git", let alone the time before GUI Git clients...
My first Linux install didn't have a GUI at all, at the start. I didn't have enough floppy disks to download all of the Slackware A, N, and X packages, so I downloaded A and a subset of N onto floppies, which let me bootstrap PPP so that I could start downloading the X packages to get a working GUI going. That was on 33k6, and only when my parents didn't want to use the phone, so it took a while...
Another problem was integrating Alpine with calendars (at least O365).
khal (with vdirsyncer) is a nice calendar app. I haven't got it working perfectly with Office635 yet though; I use a read-only url to the calendar, so I can at least see it, but cannot edit it. The Fastmail calendar works.
https://neomutt.org/ The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal. It actually makes a lot of sense as an email client and is surprisingly ergonomic. I also enjoy the fact that my config is a normal dotfile that I can version control etc. Also, your passwords can be encrypted using the tools that you choose, as opposed to whatever home grown crypto (if any) the [insert random Electr…
"The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal." I personally use (al)pine and I could not agree more. 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. So, for instance, when I send an email to one of my engineers at rsync.net, even though it is sent in pl…
> 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?
Earlier quoted context omitted.
"The guy is absolutely right. Mutt is not a gimmick like ascii video on terminal." I personally use (al)pine and I could not agree more. 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. So, for instance, when I send an email to one of my engineers at rsync.net, even though it is sent in pl…
> 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?