Daniel Micay
Daniel Micay
@ThePowerOfDreams Many users are confused about what happened. It's not as clear as it could be and many people miss the notification. It also disrupts the discussion in the room...
We currently have 10% as many room members as before (1500 vs. 15000), which is slowly growing but many of the people who were active did not get any notice...
This has happened in 2 more of rooms now, and the project has been significantly impacted by the disruption to the main room already.
@ara4n @DMRobertson Rooms bricked so far: #grapheneos:grapheneos.org (room upgraded after), #infra:grapheneos.org (room upgraded after), #dev:grapheneos.org (have not done room upgrade yet, probably need to) and potentially others we aren't aware...
This has happened again. I think it's caused by setting the rooms invite-only to deal with raids. Switching to invite-only and back appears to have a high likelihood of bricking...
There were rapid join and ban state events during the raids so it's possible that's what caused it too. It was almost certainly caused by these recent events though.
This impacts both our main room (which was recreated after the last state reset cycle) and our offtopic room.
Our main room is having state resets again. I think we'll be leaving Matrix.
If this doesn't get resolved, we're just going to be sharing our experiences with the platform in an article and moving to a platform without these problems.
You'll need to rebase this since a gradle-verification metadata error had to be fixed.