Are there any other projects using this setup? Also, any write up on the compelling reasons to switch? Are they hoping this move will attract more contributors? Article is unclear.
Synchronous Messaging at Mozilla: The Decision
11–20 of 258 posts
Re: Synchronous Messaging at Mozilla: The Decision
#12Can't wait for Mozilla to back a stable, native desktop client into a daily driver state so we can finally ditch Mattermost at work.
Seriously, I feel like it’s such an indictment on native app tool development that we have a bazillion new electron apps written by ppl all the time for weekend projects yet almost no one spitting out native apps to interface with services.
It’s clearly in demand (if a bit of a niche kind of demand)
Re: Synchronous Messaging at Mozilla: The Decision
#13Daily reminder that Rust uses Discord, a closed source piece of software with draconian privacy and data retention terms. Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
So you want mozco to go against the community's and project leaders decisions?
Do you see the problem with that line of thinking or do I have to explain further?
Re: Synchronous Messaging at Mozilla: The Decision
#14After the matrix repo hack (alright ) and the piss poor response and a complete lack of transparency (not alright) I would never touch matrix . One of the responses there was: "there is so much hate here that it is making impossible to discuss asensitive issues like security " It was the lamest excuse ever.
Are you talking about a different hack because the only hack I have heard of was not a repo hack (someone stole the SSH keys of a sysadmin via a compromised jenkins server), and they were very transparent about it.
The hack was pretty bad but I do not agree with your description of it unless you are talking about a different hack.
Re: Synchronous Messaging at Mozilla: The Decision
#15Daily reminder that Rust uses Discord, a closed source piece of software with draconian privacy and data retention terms. Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
So you want mozco to go against the community's and project leaders decisions? Do you see the problem with that line of thinking or do I have to explain further?
(Also, Rust isn't under MoCo, it's under MoFo directly.)
Re: Synchronous Messaging at Mozilla: The Decision
#16Daily reminder that Rust uses Discord, a closed source piece of software with draconian privacy and data retention terms. Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
While I'm not happy with Discord either: Mozilla does not own Rust in any way, so they cannot decide what communication tool the Rust community uses.
Re: Synchronous Messaging at Mozilla: The Decision
#17Daily reminder that Rust uses Discord, a closed source piece of software with draconian privacy and data retention terms. Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
And bad accessibility too, which I would argue goes against the Rust project's inclusivity message.
But I do not think it is up to Mozilla corporation to pick communication platform for Rust, that is not their job. The blame lies squarely on the Rust project.
Re: Synchronous Messaging at Mozilla: The Decision
#18Daily reminder that Rust uses Discord, a closed source piece of software with draconian privacy and data retention terms. Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
So you want mozco to go against the community's and project leaders decisions? Do you see the problem with that line of thinking or do I have to explain further?
Yes, if you are getting paid by someone you should do what they ask of you, especially when it's something sensible.
Re: Synchronous Messaging at Mozilla: The Decision
#19Can't wait for Mozilla to back a stable, native desktop client into a daily driver state so we can finally ditch Mattermost at work.
Seriously, I feel like it’s such an indictment on native app tool development that we have a bazillion new electron apps written by ppl all the time for weekend projects yet almost no one spitting out native apps to interface with services. It’s clearly in demand (if a bit of a niche kind of demand)
Native development on OSX and iOS both kind of suck unless you completely embrace objective C and coaca. I think that’s what’s turned so many people off to it.
It’s comparatively easy to write complex portable applications with tk (or even just strait win32 and whichever X11 widget toolkit is your favorite.)
Re: Synchronous Messaging at Mozilla: The Decision
#20Are there any other projects using this setup? Also, any write up on the compelling reasons to switch? Are they hoping this move will attract more contributors? Article is unclear.
Compelling reasons to switch: it's an open standard, it's federated (so you can own your own server and avoid vendor lock-in), it has end-to-end encryption, it supports bridging with many other protocols, there's quite a growing ecosystem of tools and libraries around it, etc.
The protocol itself is designed to be really flexible in the kind of data you can send through it (and therefore automatically propagated to and synchronized with other servers) so it can support a lot of different use cases. This includes standard chat app things like audio/video calls but it could also be used for stuff like forums or even serve as a backend for syncing information between organization (I'm thinking of things like medical information between health institutions).
All in all, there's a lot of potential in Matrix.