Live data from Hacker News

Synchronous Messaging at Mozilla: The Decision

discourse.mozilla.org

211–220 of 258 posts

Re: Synchronous Messaging at Mozilla: The Decision

#211
post #16
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.

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.

Every fulltime Rust developer is paid by Mozilla.

Saying Rust development isn't owned by Mozilla is more laughable than saying Go development isn't owned by Google.

Re: Synchronous Messaging at Mozilla: The Decision

#212

Earlier quoted context omitted.

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.

That sounds like a benefit for Matrix, but it's not obvious why Mozilla would want to spend time and money on that?

It also keeps their failures untethered to that of a centralized network.

Re: Synchronous Messaging at Mozilla: The Decision

#213
post #19
post #12

Earlier quoted context omitted.

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

> Native development on OSX and iOS both kind of suck unless you completely embrace objective C and coaca.

You can try all-Swift development with SwiftUI.

Re: Synchronous Messaging at Mozilla: The Decision

#214
post #202

Has anyone had experience with both Matrix and Mattermost? What are the main differences between the two? Apropos of nothing, currently I am running: * Signal * Wife * Family * Google Hangouts (web) * Friends and ex-coworkers * Slack * Vendor A * Vendor B * Team C * Team D * Keybase * Some friends * SMS * My Stepdaughter * Skype * Coworkers too stubborn to open Mattermost or change what they do * Mattermost * Coworke…

You've just described my nightmare scenario. I'm currently experiencing "Messaging app fatigue" and I'm not using even a quarter of the apps that you are.

Yes, fatigue is a great word for it.

Re: Synchronous Messaging at Mozilla: The Decision

#215
post #211
post #16

Earlier quoted context omitted.

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.

Every fulltime Rust developer is paid by Mozilla. Saying Rust development isn't owned by Mozilla is more laughable than saying Go development isn't owned by Google.

That’s not how governance works.

Re: Synchronous Messaging at Mozilla: The Decision

#216
post #12

Earlier quoted context omitted.

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)

You answered your own question. You can write a pretty and functional Electron app in a weekend. To implement the same level of functionality and prettiness in a native app toolkit like Qt is at least a month of work. It's the same story as Python versus C, or C versus Assembly. When C was introduced, the old-timers had the same complains like we do today: why would you program in such a slow and inefficient language…

> To implement the same level of functionality and prettiness in a native app toolkit like Qt is at least a month of work.

Qt is not native in the way that matters: using platform widgets. In fact, the choice of language really doesn't matter if you're using them right: if you have a platform-to-language bridge and it works, generally the end product is not too bad.

Re: Synchronous Messaging at Mozilla: The Decision

#217

Earlier quoted context omitted.

I guess we just prioritised working on cross-signing etc rather than adding in UI for this. Sorry; it's an oversight.

Thank you for your quick and patient answers to my perhaps too demanding questions. Cross-signing is obviously better, no question about that. However this simple UI change would be at least 95% as good, and certainly good enough to have prevented my friends from giving up on Riot. I hope that is at least somewhat constructive. Thank you for your work.

I guess https://github.com/vector-im/riot-web/issues/2735 is the bug to upvote. Annoying it's been stuck open forever :(

Re: Synchronous Messaging at Mozilla: The Decision

#218
post #201

Earlier quoted context omitted.

From two Matrix members, one who is the matrix.org team lead today: https://news.ycombinator.com/item?id=21836684

Two new full-time employees were hired to work on Dendrite (written in Go) and p2p matrix? Interesting. I had the impression that the Rust version would have priority.

Ruma isn't written by the core matrix.org team, and has its own community. Dendrite is much further along, so makes sense for us to hack on the projects we created :)

Re: Synchronous Messaging at Mozilla: The Decision

#219

Earlier quoted context omitted.

After spending several months convincing a few friends to use Riot, the ongoing fiasco with E2E has caused all of them to leave within a couple of days. Obviously they're unlikely to ever come back. It's a real shame. These are technical people who don't particularly mind verifying a key by hand. In fact I personally even prefer it. The problem is not only that certain things are not done automatically, but that the…

> Obviously they're unlikely to ever come back. I recognize this is a common attitude, but it makes no sense to me. Some software you tried today isn't designed in a way you prefer, so you go back to using something else. Okay. Makes sense. But to declare the whole project forever hopeless as if it can never be improved upon because the snapshot of your first experience with it was negative is truly irrational.

For me it is usually lost trust in the creators. If they market it like a finished product when it barely works I will not trust them anymore.

Now, if it is obvious that something is a work in progress then I personally wont mind giving it a new shot.

Re: Synchronous Messaging at Mozilla: The Decision

#220

Has anyone had experience with both Matrix and Mattermost? What are the main differences between the two? Apropos of nothing, currently I am running: * Signal * Wife * Family * Google Hangouts (web) * Friends and ex-coworkers * Slack * Vendor A * Vendor B * Team C * Team D * Keybase * Some friends * SMS * My Stepdaughter * Skype * Coworkers too stubborn to open Mattermost or change what they do * Mattermost * Coworke…

I use SMS, Slack, Discord, Skype, IRC, Google Hangouts, Facebook Messenger and WhatsApp, so you have me beat by 3. :) It would be amazing of Matrix and its bridges got good enough so I could reduce this number a bit.
Post reply on HN