Updated text a bit

src/posts/0006-modern-irc.org

@@ -8,15 +8,15 @@
 #+OPTIONS: auto-id:t
 
 #+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
-is IRC + ZNC (with replay module) + weechat (with replay script) +
-thelounge + Palaver (on iOS).
-
-The two game changer are:
-- ZNC replay module (history handled correctly)
-- ZNC palaver module (push notifications on iOS)
+is IRC. More precisely a group of different softwares togethers:
+- IRC
+- ZNC (with replay module and palaver module)
+- weechat (with replay script)
+- thelounge
+- Palaver (for iOS mobile).
 #+end_notes
 
 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?
 
-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].
-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).
    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:
 
-- 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.
   Most of the time those clients are all electron app.
-- 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.
-- anti-minimalist, I want dense /text/.
+- *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.
+- *anti-minimalist*; I want dense /text/.
   I do not want:
   + emojis,
   + images,
   + animations (gif or videos),
   + 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
   manipulations.
   A few examples:
@@ -76,27 +76,34 @@ Their major problems are:
   + get notified about missed messages,
   + get a "top messages you missed",
   + etc...
-- Prepared for EEE[fn:eee].
+- *Prepare to EEE[fn:eee]*:
   Most of those "modern" solution are a all-in-one solution, server +
   clients with generic + specific features.
   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.
 
-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
-are going a huge speed into this eternal run software development new
-ideology.
-Always evolve by adding as much new features as possible, instead of
-striving for simplicity, stability and security.
-But do we really need those features?
-People are asking for them, but we pass too much time asking about the how
-and forgetting about the why?
-Each new feature should be really studied before being developed.
+** Digression
+:PROPERTIES:
+:CUSTOM_ID: digression
+:END:
+
+The /manipulative/ part is quite important to me.
+Many users appeart to ask for those "features".
+I think this is beacause most of those people should take the time to
+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?
 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:
 :CUSTOM_ID: tutorial
 :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
 :PROPERTIES:
 :CUSTOM_ID: self-host