1314

Please don't use Discord for FOSS projects (drewdevault.com)

submitted 8 months ago by starman@programming.dev to c/opensource@lemmy.ml

411 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] toastal@lemmy.ml 0 points 8 months ago

Servers & clients use too many resources. Because of this, most have centralized around Matrix.org which kind defeats the purpose.

[-] veniasilente@lemm.ee 3 points 8 months ago

Servers & clients use too many resources.

Didn't XMPP solve that in, like, 1999?

(Really, what is with devs and nu-protocols these days? Back in my days you could run a webhost on a potato)

[-] toastal@lemmy.ml 2 points 8 months ago

The did, but Matrix is coming to reinvent that while but by wasting resources trying to duplicate the state of everything at massive storage costs & without the extensibility because JSON.

[-] iopq@lemmy.world 1 points 8 months ago

There's a Mozilla home server as well, so federation is working.

[-] toastal@lemmy.ml 2 points 8 months ago

That server is under the Matrix.org fleet. It’s like saying Edge isn’t Chrome.

[-] iopq@lemmy.world 1 points 8 months ago

The server itself doesn't matter, you can migrate it to AWS or your own physical server if you oenn the domain

[-] toastal@lemmy.ml 1 points 8 months ago

The server does matter when it comes to who is collecting all of the metadata, data, attachments. …And having that all that data centralized around a single entity is a problem.

[-] iopq@lemmy.world 1 points 8 months ago

In this case that would be Mozilla, not the host

[-] toastal@lemmy.ml 1 points 8 months ago* (last edited 8 months ago)

Matrix.org hosts Mozilla’s Matrix server. Further, the way all data is synced to all servers means if someone with a Matrix.org ID joins your room (which is most users), all data is synced to the home server. Almost all of the data is in Matrix.org’s possession & with the servers being as expensive as they are to run, more orgs shutdown when popular causing users to flock to the mother instance.