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

251–258 of 258 posts

Re: Synchronous Messaging at Mozilla: The Decision

#251

Post by pteraspidomorph »

Arathorn wrote: post #158
feanaro wrote: post #58

Earlier quoted context omitted.

There were some bug fixes in the last year (IIRC) though nothing very substantial, I think. Then again, it's always worked reasonably well for me and I'm using it regularly. I heard it was going to get worked on soon, though.

There was a major upgrade to the conference calling about 6 months ago which took it from being "barely usable" to "almost as good as Zoom". It's different semantics to Discord in that it's classic conferencing rather than a voice channel, but it works well enough for the whole core Matrix team to use it basically constantly for remote collaboration. The conferencing servers are currently in London however, so you ma…

Good to know!

Re: Synchronous Messaging at Mozilla: The Decision

#253

Post by exrook »

jeltz wrote: post #249
kibwen wrote: post #153

Earlier quoted context omitted.

What makes this possible is Cargo's "workspace" feature, which is relatively new enough that it's not hard to imagine that some older projects may simply predate it.

Hm, I have been doing this just fine without using the workspaces. What am I missing?

Cargo workspaces are more of an optimization in that they let all the crates in your project share the same output directory[0], so built dependencies can be shared among every crate, as opposed to each crate needing to (re)build all of its dependencies independently.

This helps to reduce compile times when working on projects where you frequently switch between crates.

[0] https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html

Re: Synchronous Messaging at Mozilla: The Decision

#254

Post by Ardon »

shd4 wrote: post #109

New Vector ( https://www.vector.im/ ) is hiring more designers to come work fulltime on Riot’s UI and UX as they shift Riot’s focus from being developer-led to design-led. That's great news! https://apply.workable.com/new-vector/j/6CB817C79E/

Fantastic, though I wish they weren't burdened with such a bad name. I wonder if they would ever change it...

Re: Synchronous Messaging at Mozilla: The Decision

#255

Post by erikpukinskis »

jasonzemos wrote: post #122
basilgohar wrote: post #99

Earlier quoted context omitted.

They are using a hosted provider, run by the makers of Matrix themselves. This lets them get the benefits of federation while making the hosting someone else's problem. Of course, we all want to see Mozilla bootstrap their own Matrix instance, but maybe the cost/benefit equation worked out differently for them than we would have expected. I can imagine this lets them replace IRC with a better solution faster while st…

Is Mozilla an example for the next major adopter of Matrix or are they not? If they are, and everyone else signs up for modular.im as well: at what point does this ship of Theseus called Federation only exist inside a bottle?

If it were me, I would want to a) support the existing players in the ecosystem and b) do the migration piecemeal if possible.

Working with a third party lets them start standing up rooms immediately, and get their people using the new standard without being blocked on a long process of setting up their own infra. It’s federated. They can easily migrate onto their own hardware at a later date.

It also injects money into the community they are trying to support. Even if they did start running all of their own instances, I would hope they keep a support contract with Modular for that reason.

Paying Modular + using Matrix widely immediately + beginning work on their own infrastructure is a strictly bigger shot in the arm for Matrix than just putting a couple devs on pre-planning and prototyping infra would be.

Re: Synchronous Messaging at Mozilla: The Decision

#256

Post by pabs3 »

ptman wrote: post #238
pabs3 wrote: post #221

Earlier quoted context omitted.

I really wish Telepathy took off, then you could have one single app that speaks each of those protocols and talks to the relevant servers. https://telepathy.freedesktop.org/

Matrix has bridges to many different chat systems

The bridges are server side, so you have less control over what they do.

Re: Synchronous Messaging at Mozilla: The Decision

#257

Post by pabs3 »

jeltz wrote: post #247
pabs3 wrote: post #221

Earlier quoted context omitted.

I really wish Telepathy took off, then you could have one single app that speaks each of those protocols and talks to the relevant servers. https://telepathy.freedesktop.org/

Pidgin already exists but seems to have bad support for newer protocols for some reason.

Telepathy has some architectural advantages over Pidgin. IIRC it can use Pidgin network plugins as Telepathy backends though.

Re: Synchronous Messaging at Mozilla: The Decision

#258

Post by firethief »

chrisseaton wrote: post #105
firethief wrote: post #73

Earlier quoted context omitted.

"Already"? Is that something that usually happens as a project matures?

Yes? See the fracturing of what HTML browsers supported in the 90s, or what happened to XMPP, for example.

HTML's middle ages were characterised by competing implementations of similar functionality. Inconsistency would be cause for concern, but incompleteness is expected.
Post reply on HN