Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Gianmarco Gargiulo (gianmarcogg03@mastodon.uno)'s status on Friday, 27-Jun-2025 19:53:24 JST Gianmarco Gargiulo

   @xabacadabra praticamente lo stesso problema di Matrix: sono tutti iscritti su matrix.org.

2. Embed this notice
   edu :nixos_enby: 🇵🇸 (edu@rocktriste.club)'s status on Tuesday, 24-Jun-2025 10:09:04 JST edu :nixos_enby: 🇵🇸

   in reply to

   @piuvas @rony eu subi um conduit pra testar, e o único problema “grande” que tive foi com spooling. depois de certo tempo afk, paro de receber mensagens. só recebo se eu interagir com a outra pessoa… (achei que a @beabea tinha me dado mega ghost mas era só bamblers)

   não descobri se é problema de config, do conduit, ou do matrix.org não federando direito

3. Embed this notice
   prettygood (prettygood@socially.drinkingatmy.computer)'s status on Saturday, 14-Jun-2025 16:16:59 JST prettygood

   in reply to
   @Tadano @nyanide @cornfields74 I couldn't join any rooms that were on matrix.org which pretty much killed its use for like, free software things.
4. Embed this notice
   edu :nixos_enby: 🇵🇸 (edu@rocktriste.club)'s status on Wednesday, 11-Jun-2025 08:16:54 JST edu :nixos_enby: 🇵🇸

   tentei ser diferentao, e subi um servidor Matrix na esperança de subir uma ponte pra poder usar o xampu e prosear com vcs tudo

   funcionou bem... exceto pelo fato de que as vezes as mensagens demoram 12h pra chegar em mim porque a flagship matrix.org nao gosta de federar :)

   (ou é minha arquitetura de rede maluca zoada msm)

5. Embed this notice
   nex (nex@fedi.transgender.ing)'s status on Saturday, 24-May-2025 02:23:18 JST nex

   I've seen a lot of people complaining about recent Matrix spam waves (as is understandable, it really is absolutely revolting), but then proceeding to blame it on the developer community for not dealing with it.
   I'm sorry, but I can't hold my tongue on this any longer.
   
   There ARE things happening. Moderation tooling is being spearheaded finally, but obviously this shit takes time to be developed, and unfortunately a lot of the immediate stuff is being made by smaller players like myself.
   First off, please keep in mind that Synapse and Element are not the only components in the Matrix ecosystem. There are other server implementations, and other clients, and other organizations other than New Vector Ltd and matrix.org.
   
   Here's a summary of the things I have PERSONALLY done over the past few months:
   
   1. I have implemented the new Policy Servers MSC into Meowlnir (a from-scratch moderation tool), as Element's is still closed-source and request-to-use. I created this with very lacking specification docs, and had to reverse engineer some of it to make the policy server functional.
   2. I created matrix-invite-logger to allow people to automatically log and also block incoming invites for accounts they have on servers they do not run, or when their server does not support synapse-anti-spam
   3. I have added powerful moderation tooling to clients like Gomuks, and spend time trying to urge other client developers to implement support for additional moderation tooling in their clients when I haven't had the time to open PRs myself.
   4. I have integrated registration checking into my bot's server info command so that I can see at a glance if a server is vulnerable to registration spam.
   5. I have gone out of my way to engineer a server scraper that will (when it's finished) automatically scrape Matrix to find vulnerable servers, add them to a policy list to temporarily protect rooms from them, and will either automatically contact server admins or get me to do it, to tell them that they are vulnerable.
   6. I have spent time contributing bug fixes to the most popular moderation bot on Matrix, Draupnir, used by communities like Ubuntu, Fedora, and OpenSUSE
   7. With the abrupt archival of conduwuit, I have (together with a small team) forked it into continuwuity, where we are aiming to focus on trust & safety tooling, including my experimental and trailblazing appservice callbacks to allow regular appservices to filter spam
   8. I have been pushing for room takedowns in the community moderation effort crowdsourced policy list, in order to get rid of these horrific rooms as soon as they crop up
   9. I have been making extensive contact with the Matrix Foundation to see what's going on on matrix.org, and offer advice and give feedback on their moderation
   10. I have developed a multi-account monitoring tool that currently watches a lot of public rooms for spam waves and automatically bans them before they propagate to other communities. I'm slowly getting other communities on board with this, and already have the support of several large FOSS projects
   11. I have engaged in lengthy talks with ecosystem developers to ensure that moderation tooling is getting caught up to par.
   
   (1/2)

6. Embed this notice
   Tadano (tadano@mt.watamelon.win)'s status on Tuesday, 18-Mar-2025 05:40:38 JST Tadano

   in reply to

   @get @anemone @mischievoustomato To be precise, it was initially developed by an Israeli company before being transitioned to a (suspiciously well-funded) non-profit. Additionally, joining shit often requires going through some dumb matrix.to link in my experience and the protocol had some metadata leak problems especially with it all going to matrix.org's servers. @sapphire actually blackholed that domain on his Matrix for that reason IIRC.