| 13 Jul 2021 |
 @jez:petrichor.me | i think someone was working on packaging mjolnir and making a module for it? does anyone know what the progress of that was? | 09:00:46 |
| @jez:petrichor.me | i'm particularly interested in being able to configure multiple instances of the bot, as i have 3-4 communities that i help run and wouldn't want to combine moderation for all of them | 09:01:28 |
| @jez:petrichor.me | i see the synapse module has made it into nixpkgs but not the bot https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/servers/matrix-synapse/plugins/mjolnir-antispam.nix#L22 | 09:03:15 |
| * @jez:petrichor.me should have just searched gh straight off | 09:03:59 |
| @jez:petrichor.me | https://github.com/NixOS/nixpkgs/pull/123896 | 09:04:00 |
 @fantasycookie17:artemislena.eu | In reply to @jez:petrichor.me
i think someone was working on packaging mjolnir and making a module for it? does anyone know what the progress of that was? If you have an AMD64 machine, you could use the OCI container. | 10:00:37 |
| @jez:petrichor.me | ah, that's handy, thanks! | 14:26:06 |
| @fantasycookie17:artemislena.eu | In reply to @fantasycookie17:artemislena.eu
If you have an AMD64 machine, you could use the OCI container. (if not, i.e. you're running it on ARM, the solution is a bit messy, not like it doesn't work on NixOS or messes up any system directories, and I could definitely explain how I did it if anyone's interested, but it does take more work than just declaring another Podman/Docker container) | 16:08:47 |
 hexa | Hi folks, Synapse v1.38 is now released: https://github.com/matrix-org/synapse/releases/tag/v1.38.0. Let us know if you have any problems, and don't forget to check the upgrade notes for a note on database disk usage. | 23:46:19 |
| hexa | forwareded from #homeowners:matrix.org | 23:46:39 |
| hexa | already in master :o | 23:49:55 |
| 14 Jul 2021 |
 @sumner:sumnerevans.com | In reply to @hexa:lossy.network
already in master :o I normally see the releases at around 8 US Mountain Time and then try to push the PR within an hour when there aren't any crazy dependency changes. :) | 02:45:47 |
 andi- | In case any of you also uses retention and has a homeserver that is unable to fetch history due to already existing redaction events pick the following patch into your derivation: https://github.com/matrix-org/synapse/commit/e3e73e181b2f399f3acc9fd3138d1857f0492fa9
I was a few days late to get that into 1.38 but without that patch one of my homeservers is just useless... | 08:13:14 |
| @sumner:sumnerevans.com | Oh, I bet that's the issue that I was having where after purging history, scrolling back beyond where I purged wasn't working. | 12:57:38 |
| @sumner:sumnerevans.com | Hmm... doesn't seem to have helped my situation. I still can't scroll past where I purged history. :( | 13:27:04 |
| andi- | sumner: any logs in your servers journal? | 18:25:44 |
| andi- | Mine were pretty big red transaction errors (also showing up in the postgresql log) | 18:26:00 |
| @sumner:sumnerevans.com | No, I didn't see anything insightful. | 18:26:20 |
| 16 Jul 2021 |
|  vika (she/her) 🏳️⚧️ joined the room. | 19:43:35 |
| 18 Jul 2021 |
 @andreas.schraegle:helsinki-systems.de | Is there any good reason not to delete rooms with "joined_members": 0 through the admin API? | 17:34:06 |
| @fantasycookie17:artemislena.eu | Probably not. I think it's not possible to join empty rooms anyway. | 17:43:17 |
| 19 Jul 2021 |
| @sumner:sumnerevans.com | Well, if it's a public room that you may eventually want to rejoin (or another user on your homeserver may want to join), it may be worth keeping it for a little while so that you avoid having to re-pull the room. | 00:09:36 |
| @andreas.schraegle:helsinki-systems.de | apparently I have 400-500 rooms that have no members and aren't public | 14:28:11 |
| @andreas.schraegle:helsinki-systems.de | at least according to jq '.rooms[] | select(.joined_members == 0 and .public == false) | .room_id' < rooms.json | 14:29:06 |
| @sumner:sumnerevans.com | Sounds like it is time to delete those 😄 | 14:44:33 |
 @pacien:pacien.net | what about the migrated rooms though? They still have pointers from their replacement rooms so that people can read further back in the message history | 14:46:50 |
 Dandellion | Those rooms will still have people on your server joined to them if applicable | 15:08:38 |
| 20 Jul 2021 |
 @maximilian:transformierende-gesellschaft.org | In reply to @maximilian:transformierende-gesellschaft.org
Then I suggest we monitor this closely and set the history restriction to member-only again once the PR has been included in a synapse release. So: Everything that follows now is (even more) public. Furthermore I will make ma27 an admin so I am not the only one managing this room 🙂 synapse v1.39 will include the fix: https://github.com/matrix-org/synapse/releases/tag/v1.39.0rc1
The spaces summary API now returns any joinable rooms, not only rooms which are world-readable. (#10298, #10305)
| 20:26:24 |
|  continuouswave changed their display name from cw (Vi/Vim) to continuouswave. | 20:34:50 |
| 22 Jul 2021 |
 ma27 | sumner: are you taking care of https://github.com/matrix-org/synapse/releases/tag/v1.38.1? otherwise I'd take a look at it later this afternoon :) | 14:44:27 |
