Gemfile.lock

@@ -25,10 +25,10 @@ GEM
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.8.1)
-    faraday (2.5.2)
-      faraday-net_http (>= 2.0, < 3.1)
+    faraday (2.3.0)
+      faraday-net_http (~> 2.0)
       ruby2_keywords (>= 0.0.4)
-    faraday-net_http (3.0.0)
+    faraday-net_http (2.0.3)
     ffi (1.15.5)
     forwardable-extended (2.6.0)
     gemoji (3.0.1)
@@ -210,8 +210,8 @@ GEM
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.16.3)
-    nokogiri (1.13.8-x86_64-linux)
+    minitest (5.16.2)
+    nokogiri (1.13.7-x86_64-linux)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)

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

@@ -84,9 +84,6 @@ 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! 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.
-
 In case there isn't enough confusion, retention shouldn't be confused with actual [self-destructing/disappearing messages](https://github.com/vector-im/element-meta/issues/82).
 
 *Technical note: sorry about calling <s>reference</s> homeserver implementation by the matrix.org team issue

blog/_posts/2021-12-05-matrix-community-abuse-security-by-obscurity.md

@@ -25,11 +25,21 @@ smaller steps:
    labs)
 2. Create a space.
 3. Through developer mode `/upgraderoom {{ site.matrixLatestRoomVersion }}`.
+   1. ***WARNING*** The room version number here is configured in Jekyll site
+      variable, not one specific to this post.
    2. ***WARNING*** You should check [the Matrix spec](https://spec.matrix.org/latest/rooms/)
       for the latest stable room version. Or maybe the [unstable spec](https://spec.matrix.org/unstable/rooms/)?
       Or maybe you should just [search GitHub](https://github.com/matrix-org/matrix-spec-proposals/issues?q=room%20version)?
-   3. ***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.
+      I have no idea how that works as the time of writing both are missing room versions 8 and 9.
+   3. ***WARNING*** Traditionally homeservers by other parties than Matrix.org
+      (read Synapse/Dendrite) lag behind on supported room versions and you may break
+      your room for people using those. At the time of adding this note (2021-12-14), the
+      spec v1.1 is a month and couple of days old (2021-09-11) <s>and <a href="https://gitlab.com/famedly/conduit/-/issues/161§">room version 7 is not implemented by Conduit</a></s>.
+       1. Yes, at the time of writing this post I am recommending version 9,
+          while the aforementioned variable is {{ site.matrixLatestRoomVersion }},
+          as that is what Element encourages and features such as restricted rooms
+          require and as this post hints, Matrix is even more impossible to manage
+          without those.
 4. Clear cache and reload so the old space maybe disappears.
 5. See also [Element-web#19208: Allow upgrading spaces](https://github.com/vector-im/element-web/issues/19208)
 6. Now that there is a space, right click it to create a new room under it and
@@ -88,7 +98,9 @@ you simply use `/devtools` and ban the entire server by sending a completely new
 so having to do this 20 times is nothing to you.
 
 *2022-01-10 addition:* this becomes worse as Matrix Synapse alongside [the Matrix protocol itself will authorise everything done by servers that don't honour the `m.room.server_acl` event](https://github.com/matrix-org/matrix-spec/issues/928)
-so as per the guide, you will have to acl those servers too (or the ACL might as well not exist).
+so as per the guide, you will have to acl those servers too (or the ACL might as well not exist). <s>Sadly at the time
+of writing that also includes <a href="https://gitlab.com/famedly/conduit/-/issues/67">Conduit, so all Conduits must be ACLed too</a>,
+even if they weren't malicious.</s> <s>A minor comfort is that <a href="https://gitlab.com/famedly/conduit/-/issues/161">Conduit doesn't currently support room versions 7, 8 and 9</a></s>
 
 ### Icing on the cake
 
@@ -154,3 +166,11 @@ going to stop using Matrix.
 
 * [Obligatory changelog link](https://github.com/Mikaela/mikaela.github.io/commits/master/blog/_posts/2021-12-05-matrix-community-abuse-security-by-obscurity.md)
 
+* * * * *
+
+* 2022-02-07: Conduit implemented ACL a couple of weeks ago, [Matrix Spec version is nowadays 1.2](https://matrix.org/blog/2022/02/02/matrix-v-1-2-release), but [no Element supports knocking from room version 7 (of Matrix 1.1)](https://github.com/vector-im/element-meta/issues/43) to my knowledge.
+* 2022-07-29: Conduit has had room versions 7, 8 and 9 for some time now, Matrix Spec version
+  has been at version 1.3 for a couple of weeks (2022-06-16), Dendrite has
+  supported room version 10 since around that time, Synapse has it in rc that
+  hopefully releases next week and Elements still don't support knocking
+  (from Matrix room version 7).

pages/irc/irc.markdown

@@ -39,4 +39,3 @@ links.*
 * ZNC
     * [ZNC 1.6.0 & SSL certificate verification]({% post_url blog/2015-02-24-znc160-ssl %})
     * [Installing ZNC on Ubuntu using PPA]({% post_url blog/2015-05-10-znc-ubuntu %})
-* [A couple of words on protocols (on the Discuss page)](/discuss.html/#a-couple-of-words-on-protocols)

pages/matrix.markdown

@@ -1,60 +0,0 @@
----
-layout: page
-title: '[m]'
-navigation: true
-permalink: /matrix/
-excerpt: "Matrix, a decentralised conversation store"
----
-
-Just like [IRC](/irc/), *Matrix* has became a part of my social life online. My
-room can be found from [my discuss page](/discuss) alongside
-some protocol comparison and my main accounts are in [index](/).
-
-I also have a [txt with a list of all my accounts](/txt/matrix.txt) which [has SSH signature](/txt/matrix.txt.sig).
-
-## Matrix-related posts
-
-*Note that this section is manually updated and might be missing some
-links.*
-
-* Critique
-    * [Inconsistency issues of Element, Element and Element, also privacy concerns]({% post_url blog/2021-08-03-matrix-perfect-privacy-not %})
-    * [Without selfhosting a homeserver or even then, Matrix moderation tools rely on security through obscurity]({% post_url blog/2021-12-05-matrix-community-abuse-security-by-obscurity %})
-* [A couple of words on protocols (on the Discuss page)](/discuss.html#a-couple-of-words-on-protocols)
-
-## Questions and Answers
-
-### Why so many accounts?
-
-In my opinion it's preferable to have multiple accounts on different homeservers for ensuring decentralisation instead of having a single authority in power and being able to issue commands from multiple servers in case of federation meltdown which multiple rooms experienced during the period of room version 9 before homeserver software started to nag on unintentionally open registration refusing to start.
-
-### Why do you use Matrix URI scheme instead of matrix.to?
-
-I dislike matrix.to as a concept. It's a centralized service on decentralized protocol and in my opinion it shows lack of self-esteem on Matrix side considering neither XMPP or IRC require something like it, both of those trust being known or handled appropiately.
-
-### Which client do you recommend?
-
-The one that fits your needs. Personally I mix-and-match:
-
-* FluffyChat on mobile
-  * I am a Finnish translator and moderator. It does multiple accounts.
-* hydrogen.element.io PWA mainly on mobile, sometimes on desktop
-  * It's the only Matrix client that is yet to log me out randomly, very stable, multiple account support and so far the only Matrix client running on Nokia 1 (TA-1047).
-* develop.element.io / Element flatpak on desktop
-  * `/devtools` is essential (see my critiques), and they don't support Fedora.
-* Nheko nightly flatpak on desktop
-  * I am a Finnish translator, it's actually the most Spec-complete client in my experience without long delays before something becomes supported and it's lightweight probably for being a native app instead of Electron.
-
-### Which homeserver do you recommend?
-
-I am hesistant to recommend any. Finnish users may be interested in the [Linux.fi wiki listing](https://www.linux.fi/wiki/Matrix), everyone else may be served by [joinmatrix.org listing](https://joinmatrix.org/servers/).
-
-### Why don't you run your own?
-
-As can be read between the lines from my critiques, I don't consider any homeserver to be in the state that it's either safe to run legally or lightweight enough or not require constant maintenance as opposed to IRC which I do selfhost.
-
-The world situation in general discourages me from anything as heavy.
-
-* * * * *
-
-*The lucky Matrix number is `{{site.matrixLatestRoomVersion}}`, but do [consult the Spec for that](https://spec.matrix.org/latest/rooms/#complete-list-of-room-versions) and definitely ask `!servers upgrade {{site.matrixLatestRoomVersion}}` from [Version Checker](matrix:u/version:maunium.net) or [Fluff Generator](matrix:u/+:jae.fi) or [their siblings](https://github.com/maubot/rsvc).*