it is highly disorienting and stress-inducing to wake up one day to discover infrastructure you had ties to for over 10 years yanked from underneath you
one can only imagine how much worse it's for freenode staff
4
16
231
Conversation
(yes, there was an advance notice, a few days, for the freenode to liberachat migration, but it wasn't entirely obvious at first what sort of action and how quickly will be needed, so it didn't help that much)
1
2
62
Replying to
Since libera.chat didn't start with a clone of the freenode data, I didn't really see much advantage of trying to move there.
If I'm going to need to spend weeks nagging people to move, might as well be to Matrix, where our new rooms aren't tied to a specific server.
2
4
as in, moving to a different IRC network is disruptive, but less so than to Matrix
1
1
Replying to
We started with the IRC channel as the main room and used an inherently bridged Matrix room.
However, 90% of the users in the channel ended up being on Matrix. Main disruption for us is needing to move to standalone Matrix rooms. It's fine since we needed to upgrade room anyway.
Since most users are on Matrix, our IRC channels aren't particularly useful without being bridged. The bridge was terrible there's no way we're using that approach again.
So, we do have #grapheneos and #grapheneos-offtopic on libera.chat but they're totally dead.
1
2
The only way those channels would be useful is if we deployed a bridge, but it would have to be a leaner one not requiring moderation powers on Matrix. The way that worked was unacceptably invasive and awful. A traditional bridge bot would be fine but the UX is awful for those.
1
Show replies
Replying to
It ended up this way because we treated them as equal and always referenced it as a bridged Matrix/IRC channel with people having a choice of platform.
I preferred IRC which is why that was the canonical channel, but our users clearly prefer Matrix and Telegram over it, by far.
1
2
Show replies