Updated text a bit
This commit is contained in:
parent
6adfe0ba7d
commit
91c850b7fe
1 changed files with 46 additions and 30 deletions
|
@ -8,15 +8,15 @@
|
||||||
#+OPTIONS: auto-id:t
|
#+OPTIONS: auto-id:t
|
||||||
|
|
||||||
#+begin_notes
|
#+begin_notes
|
||||||
tl;dr: Why and how IRC.
|
tl;dr: Why and how to have modern and respectful chat system with IRC.
|
||||||
|
|
||||||
After reviewing and testing many different chat solutions the clear winner
|
After reviewing and testing many different chat solutions the clear winner
|
||||||
is IRC + ZNC (with replay module) + weechat (with replay script) +
|
is IRC. More precisely a group of different softwares togethers:
|
||||||
thelounge + Palaver (on iOS).
|
- IRC
|
||||||
|
- ZNC (with replay module and palaver module)
|
||||||
The two game changer are:
|
- weechat (with replay script)
|
||||||
- ZNC replay module (history handled correctly)
|
- thelounge
|
||||||
- ZNC palaver module (push notifications on iOS)
|
- Palaver (for iOS mobile).
|
||||||
#+end_notes
|
#+end_notes
|
||||||
|
|
||||||
How to chat in 2019? Certainly with slack, or via a social media app in the
|
How to chat in 2019? Certainly with slack, or via a social media app in the
|
||||||
|
@ -24,9 +24,9 @@ browser or mobile phone app.
|
||||||
|
|
||||||
How geeks should chat in 2019?
|
How geeks should chat in 2019?
|
||||||
|
|
||||||
To answer this question here is my opinion (after having tried many
|
To answer this question here is my opinion after having tried many
|
||||||
different chat solutions[fn:tries].
|
different chat solutions[fn:tries].
|
||||||
Here are the feature I think a modern geeky solution should have:
|
Here are the feature I think a modern solution should have:
|
||||||
|
|
||||||
1. *terminal client* or *terminal-like UI* (in emacs for example).
|
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
|
All modern UI looks cool for screenshots, but if you are going to use it
|
||||||
|
@ -55,19 +55,19 @@ I am quite disappointed by /modern/ chat applications.
|
||||||
|
|
||||||
Their major problems are:
|
Their major problems are:
|
||||||
|
|
||||||
- prodigal; most those client applications (slack, gitter, riot,
|
- *resource-heavy*; most those client applications (slack, gitter, riot,
|
||||||
mattermost, etc...) easily consume more than 300MB of RAM.
|
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 all electron app.
|
||||||
- not private. Most solution do not encrypt your conversations. Even
|
- *not private*; most solution do not encrypt your conversations.
|
||||||
if using encryption mechanism and you trust your client, and you will
|
Even if using encryption mechanism and you trust your client, and you
|
||||||
still reveal your social network topology.
|
will still reveal your social network topology.
|
||||||
- anti-minimalist, I want dense /text/.
|
- *anti-minimalist*; I want dense /text/.
|
||||||
I do not want:
|
I do not want:
|
||||||
+ emojis,
|
+ emojis,
|
||||||
+ images,
|
+ images,
|
||||||
+ animations (gif or videos),
|
+ animations (gif or videos),
|
||||||
+ HTML/Markdown display
|
+ HTML/Markdown display
|
||||||
- Manipulative; they try very hard to optimize engagement.
|
- *manipulative*; they try very hard to optimize engagement.
|
||||||
This is generally achieved through FOMO[fn:FOMO] and social anxiety
|
This is generally achieved through FOMO[fn:FOMO] and social anxiety
|
||||||
manipulations.
|
manipulations.
|
||||||
A few examples:
|
A few examples:
|
||||||
|
@ -76,27 +76,34 @@ Their major problems are:
|
||||||
+ get notified about missed messages,
|
+ get notified about missed messages,
|
||||||
+ get a "top messages you missed",
|
+ get a "top messages you missed",
|
||||||
+ etc...
|
+ etc...
|
||||||
- Prepared for EEE[fn:eee].
|
- *Prepare to EEE[fn:eee]*:
|
||||||
Most of those "modern" solution are a all-in-one solution, server +
|
Most of those "modern" solution are a all-in-one solution, server +
|
||||||
clients with generic + specific features.
|
clients with generic + specific features.
|
||||||
That way, some feature will be only possible in their client or that will
|
That way, some feature will be only possible in their client or that will
|
||||||
push concurrent app developers to follow the pace of new features.
|
push concurrent app developers to follow the pace of new features.
|
||||||
|
|
||||||
The /manipulative/ part is quite important in fact.
|
|
||||||
Many of those "features" are in fact wanted by the users.
|
|
||||||
I think this is because those people should take the time to reflect about
|
|
||||||
the real plus value of those features vs their price.
|
|
||||||
Like it is state in Digital Minimalism[fn:dm].
|
|
||||||
|
|
||||||
Even recent projects like matrix, mastodon that thrive to break monopolies
|
** Digression
|
||||||
are going a huge speed into this eternal run software development new
|
:PROPERTIES:
|
||||||
ideology.
|
:CUSTOM_ID: digression
|
||||||
Always evolve by adding as much new features as possible, instead of
|
:END:
|
||||||
striving for simplicity, stability and security.
|
|
||||||
But do we really need those features?
|
The /manipulative/ part is quite important to me.
|
||||||
People are asking for them, but we pass too much time asking about the how
|
Many users appeart to ask for those "features".
|
||||||
and forgetting about the why?
|
I think this is beacause most of those people should take the time to
|
||||||
Each new feature should be really studied before being developed.
|
reflect about the real plus value of those features vs their price.
|
||||||
|
As it is stated in Digital Minimalism[fn:dm], those feature are not the
|
||||||
|
real reason you use it.
|
||||||
|
I think this is an instance of the recent software development:
|
||||||
|
|
||||||
|
The idea that software MUST evolve and change.
|
||||||
|
Add as much new features as possible, instead of striving for simplicity,
|
||||||
|
stability and security.
|
||||||
|
|
||||||
|
We pass too much time asking about the how and forgetting about the why?
|
||||||
|
I would rather prefer a system that does not evolve much but study the real
|
||||||
|
full impact of adding a new feature to it.
|
||||||
|
And I think some software should be considered *finished* (like TeX).
|
||||||
|
|
||||||
Would that feature be a full total net positive for everyone?
|
Would that feature be a full total net positive for everyone?
|
||||||
Or is there a price to pay? The price is generally the size and complexity
|
Or is there a price to pay? The price is generally the size and complexity
|
||||||
|
@ -155,6 +162,15 @@ and finally abandoned (I certainly forgot a few ones):
|
||||||
:PROPERTIES:
|
:PROPERTIES:
|
||||||
:CUSTOM_ID: tutorial
|
:CUSTOM_ID: tutorial
|
||||||
:END:
|
:END:
|
||||||
|
|
||||||
|
Here is how to have a great private self-hosted IRC server to share with a
|
||||||
|
small group of people.
|
||||||
|
|
||||||
|
If this appear to be too much work for you, you should simply use a service
|
||||||
|
that host a znc bouncer for you (I found some apparently free services
|
||||||
|
doing that) and find an IRC server allowing you to create some private
|
||||||
|
channel.
|
||||||
|
|
||||||
** Self Host
|
** Self Host
|
||||||
:PROPERTIES:
|
:PROPERTIES:
|
||||||
:CUSTOM_ID: self-host
|
:CUSTOM_ID: self-host
|
||||||
|
|
Loading…
Reference in a new issue