> effectively using Matrix as a big decentralised IRC bouncer in the sky.
No. In theory it is, but in practice it's a big centralized IRC bouncer in the sky where everyone is reliant on riot.im servers.
Synchronous Messaging at Mozilla: The Decision
71–80 of 258 posts
Re: Synchronous Messaging at Mozilla: The Decision
#72Wow this already looks like a fractured mess! https://matrix.org/clients/ Why are there so many clients with different supported functionality?
That page could have (much) better UX - n.b. that it defaults to showing you only Linux clients; you have to click around to filter by other platforms. It also is outdated and misses many of the newer exciting clients such as http://dittochat.org/ or https://github.com/kiliankoe/nio. A more comprehensive view can be found at https://matrix.org/docs/projects/try-matrix-now/. Updating all this is on the todo list, but writing software >> writing website atm.
Re: Synchronous Messaging at Mozilla: The Decision
#73Wow this already looks like a fractured mess! https://matrix.org/clients/ Why are there so many clients with different supported functionality?
"Already"? Is that something that usually happens as a project matures?
Re: Synchronous Messaging at Mozilla: The Decision
#74Earlier quoted context omitted.
Have you tried RiotX https://play.google.com/store/apps/details?id=im.vector.riot... Most efforts are going to this new android client. The issue you refer to has been properly handled on RiotX (soft logout)
I don't think this issue is related to soft logout, which is what happens when the user logs out of a device remotely. The issue I was running into was that the app, after 24 hours of being logged in, would get stuck in an initialization loop.
Sry, to be more precise, token invalidation has been properly handled in riotX as part of the soft logout feature;
Re: Synchronous Messaging at Mozilla: The Decision
#75Earlier quoted context omitted.
I don't think this issue is related to soft logout, which is what happens when the user logs out of a device remotely. The issue I was running into was that the app, after 24 hours of being logged in, would get stuck in an initialization loop.
Sry, to be more precise, token invalidation has been properly handled in riotX as part of the soft logout feature;
Oh, awesome! I just installed Riot 0.9.9, so I'm going to test that out and see if the issue occurs. After that I'll switch to RiotX and check there as well and report any issues I find.
Re: Synchronous Messaging at Mozilla: The Decision
#76Earlier quoted context omitted.
Agreed, this is a huge relief. I was getting quite worried that Mozilla would go to Discord, like Rust and other projects have done. I don't know anything about Matrix, but I know it's free, and if it has Mozilla's endorsement, now I'm actually curious to try it... maybe even via an IRC bridge!
FYI #rust-beginners is on discord, but many of the teams have transitioned to Zulip because it has threads. I'd love if Zulip was OSS, but at least it's a highly innovative company that's improved a lot on the UX of IRC (far beyond not needing to setup a bouncer). The mismatch between Discord's targeted audience of gamers can get funny at times. One rust dev has had their status we to "playing systemd" for days. Edit…
I wouldn't describe Zulip as coming from the IRC tradition -- it was built by MIT students as an improvement on MIT's Zephyr. There's a split between line-at-a-time messaging like IRC or Slack, and paragraphs-at-a-time messaging with per-message channels like Zephyr, Gale, and now Zulip.
I really miss the paragraphs style.
Re: Synchronous Messaging at Mozilla: The Decision
#77This is really good news. I have only one question for Mozilla: why choose a solution whose hallmark is decentralization and the libre model- only to become a customer of a centralized host (modular.im). Why can't Mozilla actually federate? That's a step backward from your IRCd in my opinion. I hope Mozilla gets onboard with everyone else running their own Synapse, hacks on it, and pay their dues with patches, rather…
What benefits would Mozilla get from running their own server and federation (that they have with ircd today)?
Re: Synchronous Messaging at Mozilla: The Decision
#78> effectively using Matrix as a big decentralised IRC bouncer in the sky. No. In theory it is, but in practice it's a big centralized IRC bouncer in the sky where everyone is reliant on riot.im servers.
Not really: anyone can run an IRC bridge, and many people do. The #mozilla_#wherever:matrix.org namespace is the preexisting moznet bridge run by Matrix.org (not Riot.im), but anyone with their own server could also run their own bridge, much like they could run their own bouncer today. There is then additional decentralisation from the fact that the room history is replicated throughout all the participating Matrix servers.
Re: Synchronous Messaging at Mozilla: The Decision
#79> we have decided to replace IRC with Riot/Matrix, hosted by Modular.IM.
Looking at the pricing on modular.im[1] it starts at $10/month for up to 5 "active users," $73/m for up to 50, on and up..
Though modular's credentials look good, it seems like there'd be scope for some serious price gouging if Matrix had more takeup.
The standard (android) client's default servers are patchy enough to make this worth looking into, IME.
Re: Synchronous Messaging at Mozilla: The Decision
#80This is really good news. I have only one question for Mozilla: why choose a solution whose hallmark is decentralization and the libre model- only to become a customer of a centralized host (modular.im). Why can't Mozilla actually federate? That's a step backward from your IRCd in my opinion. I hope Mozilla gets onboard with everyone else running their own Synapse, hacks on it, and pay their dues with patches, rather…
What benefits would Mozilla get from running their own server and federation (that they have with ircd today)?
Good publicity for decentralization. If they can get it to work, it shows that it’s possible to run a large instance from a non-central host.