Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Synchronous Messaging at Mozilla: The Decision

discourse.mozilla.org

Post reply on HN
Print view View original

41–50 of 258 posts

Re: Synchronous Messaging at Mozilla: The Decision

#41

Post by jordigh »

jeltz wrote: post #7

Nice, given how the discussions were going some months ago I was worried that they would pick some closed source solution like Discord or Slack. I have not used Matrix so I do not know how good it is, but I do not like the lock-in of Discord and Slack.

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!

Re: Synchronous Messaging at Mozilla: The Decision

#43

Post by billCarsonFr »

dstaley wrote: post #39

I really hope this means more development and focus on building great mobile apps for Matrix. For the past four months the Riot Android app has had this bug where login state expires after a day and the app gets stuck in an infinite loop trying to refresh the token. Supposedly a fix was merged [1], but after four months of not being able to use Riot (and thus Matrix) my friend group has fallen back to Discord. [1] ht…

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)

Re: Synchronous Messaging at Mozilla: The Decision

#44

Post by steveklabnik »

pcwalton wrote: post #26
dzypa wrote: post #8

Daily 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.

> Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah Baiting people like this is inherently uncivil. > the Mozilla Corporation should not have allowed it. Mozilla has no say over what the Rust community does.

Yep, thank you, on both counts.

Re: Synchronous Messaging at Mozilla: The Decision

#45

Post by ReverseCold »

est31 wrote: post #28
kibwen wrote: post #5

I'm pleasantly surprised! They took the route of "promising but underdeveloped technology" rather than settling for a well-developed solution that compromises their principles (which, frankly, I wouldn't have faulted them for; at the end of the day you still have to get work done). With luck maybe we'll see Mozilla contribute to Matrix? There is, after all, an implementation written in Rust: https://github.com/ruma

The last ruma commit was in August, which was after a long period where nothing happened at all. Is the project dead?

The author says they’re waiting on Rust and Matrix features/documentation. There’s an open issue with more details

https://github.com/ruma/ruma/issues/189

Re: Synchronous Messaging at Mozilla: The Decision

#46

Post by steveklabnik »

icebraining wrote: post #24
dzypa wrote: post #18

Earlier quoted context omitted.

Yes, if you are getting paid by someone you should do what they ask of you, especially when it's something sensible.

Most Rust contributors are not Mozilla employees. Even in the core team, 3 of 9 members weren't (as of 2017, may be different today),

It is 3 of 9 today as well. (In 2017 it was higher!)

Re: Synchronous Messaging at Mozilla: The Decision

#47

Post by pteraspidomorph »

feanaro wrote: post #20
nickstinemates wrote: post #11

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.

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 a…

I try matrix on occasion (as in, I set up my own server from scratch). The last time I tried it, support for multi-participant audio and video calls (and screensharing) was still between terrible and nonexistant. Definitely much worse than Discord. Has it improved?

Re: Synchronous Messaging at Mozilla: The Decision

#48

Post by steveklabnik »

est31 wrote: post #38
gsnedders wrote: post #15

Earlier quoted context omitted.

(Also, Rust isn't under MoCo, it's under MoFo directly.)

In which way? I've thought the Rust engineers were employees of the Mozilla corporation? And the Rust trademark seems to be owned by the Mozilla corporation as well: https://tsdr.uspto.gov/#caseNumber=87796977&caseSearchType=U...

All Mozilla employees working on Rust are under Moco, not Mofo, that's correct. Unless something extremely drastic that nobody has talked about has happened in the last year.

Almost all of Mozilla is under Moco.

Re: Synchronous Messaging at Mozilla: The Decision

#49

Post by [deleted] »

dzypa wrote: post #8

Daily 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.

[deleted]

Re: Synchronous Messaging at Mozilla: The Decision

#50

Post by kibwen »

est31 wrote: post #28
kibwen wrote: post #5

I'm pleasantly surprised! They took the route of "promising but underdeveloped technology" rather than settling for a well-developed solution that compromises their principles (which, frankly, I wouldn't have faulted them for; at the end of the day you still have to get work done). With luck maybe we'll see Mozilla contribute to Matrix? There is, after all, an implementation written in Rust: https://github.com/ruma

The last ruma commit was in August, which was after a long period where nothing happened at all. Is the project dead?

I actually interviewed the author in August for our Rust podcast, on which he says he's waiting for async to mature before progressing further: https://rustacean-station.org/episode/001-ruma/
Post reply on HN