Live data from Hacker News

Synchronous Messaging at Mozilla: The Decision

discourse.mozilla.org

121–130 of 258 posts

Re: Synchronous Messaging at Mozilla: The Decision

#122

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

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?

Re: Synchronous Messaging at Mozilla: The Decision

#123

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

Assuming the purpose of the messaging system selected is to help Mozilla's community work together on Mozilla projects, what benefit of 'decentralization' do you think would improve their ability to work together effectively?

Re: Synchronous Messaging at Mozilla: The Decision

#124

Earlier quoted context omitted.

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.

Wait, why can't you type a paragraph at a time in IRC?

Re: Synchronous Messaging at Mozilla: The Decision

#125
post #50
post #28

Earlier quoted context omitted.

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/

I love the name of your podcast.

Re: Synchronous Messaging at Mozilla: The Decision

#126
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…

This is not at all the same thing. Programs written in C aren't inherently low-quality, everything abusing the web stack as an application platform – including Electron – is.

Re: Synchronous Messaging at Mozilla: The Decision

#127

Wow this already looks like a fractured mess! https://matrix.org/clients/ Why are there so many clients with different supported functionality?

It's called "freedom of choice". The alternative is for Facebook, GOSPLAN or Apple to decide what features and UI you get.

Re: Synchronous Messaging at Mozilla: The Decision

#128
post #50

Earlier quoted context omitted.

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/

I love the name of your podcast.

Thanks! Also, while we're here, let me advertise that this is not just "my" podcast, it's a community-based podcast that accepts audio files from anyone who wants to make any Rust-related podcast content but who doesn't want to go through the trouble of setting up a website, file hosting solution, podcast index integration, and so on. Contributions accepted. :) https://github.com/rustacean-station/rustacean-station.org/

Re: Synchronous Messaging at Mozilla: The Decision

#130
post #101

Earlier quoted context omitted.

If Mozilla will use their own domain name they will be free to move their federated Matrix instance wherever they want. Modular.im will only provide the hosting expertise. I expect that in the future self-hosting your own Matrix server instance will become much easier.

It can be a bit onerous, half the convo in our matrix room is about updating matrix.

I don’t have experience with running Synapse but it looks like a beast. Dendrite and Ruma look very promising though; can’t wait to have a lightweight home-server ready for prime-time.
Post reply on HN