discuss: mention Hydrogen, credit where it's due

Resolves: #337

Gemfile.lock

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.0.5)
+    activesupport (7.0.6)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
@@ -24,7 +24,7 @@ GEM
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.8.1)
-    faraday (2.7.7)
+    faraday (2.7.9)
       faraday-net_http (>= 2.0, < 3.1)
       ruby2_keywords (>= 0.0.4)
     faraday-net_http (3.0.2)

blog/_posts/2021-08-03-matrix-perfect-privacy-not.md

@@ -94,6 +94,12 @@ and as your room is hosted on every homeserver that has users in your room,
 have a single homeserver that hasn't explicitly enabled it, or doesn't otherwise support it, and the room
 history never goes away. Executing `/upgraderoom {{site.matrixLatestRoomVersion}}` or any other version [will also remove the event](https://github.com/matrix-org/synapse/issues/11279).
 
+**_WARNING!_** [Enabling history **_retention_** may **_corrupt your Synapse database_**](https://github.com/matrix-org/synapse/issues/13476)
+and [will make your room **_unrejoinable_** if a homeserver leaves it for long enough](https://github.com/matrix-org/synapse/issues/11448).
+Upgrading the room will fix that, but it's just a fancy
+way of saying "discontinue the old room and add a note saying where the new
+room is".
+
 **_WARNING! Always before executing `/upgraderoom` check that everyone in your room has a recent Matrix server that supports your target room version, otherwise you may lock some of your users out._** For example `/invite @version:maunium.net` and once it joins, say
 `!servers upgrade {{site.matrixLatestRoomVersion}}` to get a list of servers that don't support room version {{site.matrixLatestRoomVersion}} yet.
 
@@ -187,3 +193,5 @@ or you can find me from a lot of the linked issues and there is also [issue trac
       to not be confused with retention.
     - Oh and reply fallbacks leaking previously encrypted messages too.
   - 2022-05-31: I noticed that Element iOS has gotten pills. Strikethrough time.
+  - 2023-07-05: I added warning that room retention may cause database
+    corruption and make room unrejoinable.

pages/discuss.markdown

@@ -90,6 +90,11 @@ past.
   _I am not interested in even trying to selfhost a Matrix (home)server and bridges
   until the situation significantly improves_. _[Matrix clients also seldom support connecting through Tor easily](https://github.com/vector-im/element-meta/issues/200)_,
   while the _[Synapse server by Matrix.org team doesn't support connecting](https://github.com/matrix-org/synapse/issues/5152) through [I2P or Tor](https://github.com/matrix-org/synapse/issues/5455) at [all](https://github.com/matrix-org/synapse/issues/7088)_.
+  - Exception: [Hydrogen](https://hydrogen.element.io) ([GitHub](https://github.com/vector-im/hydrogen-web))
+    is the only client I have encountered that works well on Nokia 1 TA-1047
+    or in other words passes the so-called toaster test. It does self-describe
+    as _A minimal Matrix chat client, focused on performance, offline
+    functionality, and broad browser support_, which it redeems.
 
 ## And on transports, relays and bridges
 

pages/matrix.markdown

@@ -142,20 +142,7 @@ They are related to bringing Matrix to other protocols or vice versa.
 The public/world-readable history visibility option means exactly what it says,
 public even without joining the room. These rooms are accessible to tools
 such as [Matrix Static](https://view.matrix.org/) and its successor [Matrix Public Archive](https://github.com/matrix-org/matrix-public-archive)
-(aka `@archive:matrix.org`) and thus their history is visible in search engines. If this isn't what you
-want, set history visibility to one of the members only options (since
-selecting this option, since being invited or since join).
-
-Additionally [Matrix Foundation considers members-only history as public and will show it to anyone through archive.matrix.org](https://github.com/matrix-org/matrix-public-archive/blob/main/docs/faq.md#why-does-the-archive-user-join-rooms-instead-of-browsing-them-as-a-guest). Thus if you have a semi-public room on Matrix, you should follow these steps:
-
-- Set your room history visibility to "since user joined the room" or at least
-  "since the user was invited".
-- Set the room join rule to `knock` or `invite` -only. If you really need to,
-  you may also use `restricted` or `knock_restricted`, but be careful to not
-  allow access from public rooms (although this will still protect you from
-  matrix-public-archive).
-- Consider enabling end-to-end-encryption while it's generally not adviced for
-  public rooms.
+(aka `@archive:matrix.org`) and thus their history is visible in search engines.
 
 Note that as the option name hints, the history visibility option will not
 apply to previous messages. Thus if you first make room public and then
@@ -173,9 +160,12 @@ and related issues.
 It depends.
 
 You can try [Matrix Public Archive](https://github.com/matrix-org/matrix-public-archive/), e.g. for Matrix HQ [archive.matrix.org/r/matrix:matrix.org](https://archive.matrix.org/r/matrix:matrix.org)
+or [matrix-archive.evulid.cc/r/matrix:matrix.org](https://matrix-archive.evulid.cc/r/matrix:matrix.org)
 omitting the leading `#`.
 
-_If you too consider that undesirable, you can [join us at matrix-org/matrix-public-archive#47 requesting the ability to opt-out](https://github.com/matrix-org/matrix-public-archive/issues/47) and ban `@archive:matrix.org` from your rooms in hopes that it will be enough._
+_Until 2023-06-27 [Matrix Foundation considered members-only rooms as public](https://matrix.org/blog/2023/07/what-happened-with-the-archive#a-note-on-shared-history-visibility)
+so some outdated or patched archive instances may still reveal information.
+[Method to opt-out is still not in sight.](https://github.com/matrix-org/matrix-public-archive/issues/47)_
 
 Alternatively if the room in question has an alias, you can try poking the room directory API e.g. for [#matrix.fi:matrix.org](matrix:r/matrix.fi:matrix.org): [https://matrix-client.matrix.org/\_matrix/client/v3/directory/room/%23matrix.fi%3Amatrix.org](https://matrix-client.matrix.org/_matrix/client/v3/directory/room/%23matrix.fi%3Amatrix.org), you get the room ID and list of homeservers in it and if you see a single user (or otherwise not so popular homeserver), you can make educated guesses on who may be in the room. Note that this particular link requires `matrix.org` to be in the room and aware of the alias.
 
@@ -602,9 +592,14 @@ Matrix has a place in my heart, just as IRC and XMPP and while none of the three
 get resolved and the fighting between them to end and I am tired of the "stop having fun" or "you are worse person for still using deprecated IRC"
 or "I wish IRC/XMPP just died already as it's so old" or whatever attitude I see amongst certain Matrix user/enthustiastic groups.
 
-However I admit having increasingly difficult time believing that either _Matrix
+However I admit sometimes having difficult time believing that either _Matrix
 Foundation_ or _New Vector trading as Element_ has their users best interests
-in heart.
+in heart. On my worse days, I especially hardwordedly criticse [media never being removed](https://github.com/matrix-org/synapse/issues/1263#issuecomment-1120225193)
+or [fear that Matrix may endanger gender or sexual minorities by leaking room-specific profiles](https://github.com/matrix-org/synapse/issues/5677#issuecomment-894831845)
+and especially [lack of self-destructing messages (that is nowadays a discussion rather than an issue)](https://github.com/vector-im/element-meta/discussions/682#discussioncomment-3803806)
+considering even [DeltaChat (also known as an email client](https://delta.chat)
+manages to implement it without control over the underlying protocol and even
+less guarantees!
 
 ---