Fix & improve old posts
This commit is contained in:
parent
0e9325403b
commit
0e0f00f9d6
|
@ -27,15 +27,15 @@ browser or mobile phone app.
|
|||
|
||||
How geeks should chat in 2019?
|
||||
|
||||
To answer this question here is my opinion after having tried many
|
||||
This post is about my opinion on the subject after having tried many
|
||||
different chat solutions[fn:tries].
|
||||
Here are the feature I think a modern solution should have:
|
||||
Here is a list of the features I think a modern solution should have:
|
||||
|
||||
1. *terminal client* or *terminal-like UI* (in emacs for example).
|
||||
All modern UI looks cool for screenshots, but if you are going to use it
|
||||
a lot, you will prefer density over good looking.
|
||||
Most app, web app are terrible related to information by number of pixel
|
||||
ratio.
|
||||
Most web apps are terrible when looking at delivered information by
|
||||
number of pixels ratio.
|
||||
2. *multi-platform*: If you do not have a terminal at hand (or emacs) then,
|
||||
you should be able to get your message on your phone or via a web
|
||||
interface for portability.
|
||||
|
@ -49,9 +49,10 @@ Here are the feature I think a modern solution should have:
|
|||
Chat should be about TEXT, not images, not videos, not presentations and
|
||||
PDF.
|
||||
7. *No anti-features*: show when someone is typing, show when someone
|
||||
as read your message, etc... Those functionality are in fact increasing
|
||||
social insecurity and forces you to answer sooner instead of really
|
||||
taking the time to answer correctly.
|
||||
as read your messages, etc... Those functionalities increase your
|
||||
social insecurities feeling. They forces you to answer sooner instead of
|
||||
really take the time to answer correctly. You can read Digitial
|
||||
minimalism to know more about that subject[fn:dm].
|
||||
8. *Free software*
|
||||
|
||||
I am quite disappointed by /modern/ chat applications.
|
||||
|
@ -60,7 +61,7 @@ Their major problems are:
|
|||
|
||||
- *resource-heavy*; most those client applications (slack, gitter, riot,
|
||||
mattermost, etc...) easily consume more than 300MB of RAM.
|
||||
Most of the time those clients are all electron app.
|
||||
Most of the time those clients are electron applications.
|
||||
- *not private*; most solution do not encrypt your conversations.
|
||||
Even if using encryption mechanism and you trust your client, and you
|
||||
will still reveal your social network topology.
|
||||
|
@ -207,7 +208,7 @@ server {
|
|||
gzip off;
|
||||
proxy_redirect off;
|
||||
|
||||
## Some requests take more than 30 seconds.
|
||||
## Some requests take more than 30 seconds.
|
||||
proxy_read_timeout 30s;
|
||||
proxy_connect_timeout 30s;
|
||||
|
||||
|
@ -218,10 +219,10 @@ server {
|
|||
proxy_set_header X-Forwarded-Ssl on;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
proxy_set_header X-Forwarded-Proto $scheme;
|
||||
proxy_set_header X-Client-Verify SUCCESS;
|
||||
proxy_set_header X-Client-DN $ssl_client_s_dn;
|
||||
proxy_set_header X-SSL-Subject $ssl_client_s_dn;
|
||||
proxy_set_header X-SSL-Issuer $ssl_client_i_dn;
|
||||
proxy_set_header X-Client-Verify SUCCESS;
|
||||
proxy_set_header X-Client-DN $ssl_client_s_dn;
|
||||
proxy_set_header X-SSL-Subject $ssl_client_s_dn;
|
||||
proxy_set_header X-SSL-Issuer $ssl_client_i_dn;
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
@ -43,9 +43,9 @@ So here is my piece of code I added to my doom-emacs =config.el=:
|
|||
(t 'doom-laserwave))))
|
||||
(when (not (equal doom-theme theme))
|
||||
(setq doom-theme theme)
|
||||
(load-theme doom-theme t)
|
||||
;; run that function again next hour
|
||||
(run-at-time (format "%02d:%02d" (+ hour 1) 0) nil 'y/update-time))))
|
||||
(load-theme doom-theme t))
|
||||
;; run that function again next hour
|
||||
(run-at-time (format "%02d:%02d" (+ hour 1) 0) nil 'y/auto-update-theme)))
|
||||
|
||||
(y/auto-update-theme)
|
||||
#+END_SRC
|
||||
|
|
Loading…
Reference in New Issue