In these companies, does anyone check the licenses in details to make sure using them is ok for the company?

Meta will get at least the metadata: meaning they will record who was in which call connecting from where.

For example, if one member is visiting a client, Meta may be able to infer the relation between the 2 companies.

If any of the people in the room click “report”, then the discussion is sent for review without the encryption protection

I’m pretty sure their user agreement translates to “you agree to let us do whatever the f*ck we want with the data you’re purposely disclosing to us”.

And last but not least: if Meta decides to wipe the archives, any info get lost?

There a reasons large companies ban unauthorized apps to talk about work.

XMPP is so bad it was the baseline for Whatsapp. You know: that minor platform that feels like IRC and never took off. A lot of the techno around you are old stuff that evolved, “new” techno usually comes with new unexpected issues. Then they mature, get better and… old?

Am I the only one who thinks that you could really please a lot of gamers by just taking old popular games with updated graphics, music, sounds and release as they were?

Alternative answer: "We understand your issue and will fix it as time and priorities allow. Please note that customers paying for support always get higher priority. Given MS contributions to the project, this ticket was ranked 42nd in our priority list.

Have a pleasant day! FFMPEG support team"

I’m sorry if that’s harsh, but my feedback would be: drop that chart!

It’s daunting, it’s going to freak out many newbies. Too much choice kills the choice.

You have one “default” at the bottom, Mint, so stick to that. Tell the newbies they can switch anytime to something else once they’re a bit more comfortable with the Linux-world. And if I’m not mistaken, you can install and try the main DEs with Mint also. Or you can recommend Ubuntu, or any other newbie friendly distro. Just pick one and don’t lose them over what they could see as an important difficult decision before they even get started.

Mozilla downsizes as it refocuses on Firefox and AI drops multiple products and layoff 60 so that its current budget can accomodate the stratospheric compensation of its new CEO.

This might be an unpopular post but so’ll be it: Mastodon is the existing proof that Meta could kill Mastodon any time.

Mastodon was using a protocol compatible with GNU Social: OStatus, but some features were quickly added without consideration for other implementations.

So when per-post privacy were introduced, for example, they were very public on GNU Social, because their devs had no idea this was coming. And GNU Social was blamed for it.

https://privacy.thenexus.today/mastodon-a-partial-history/#mastodon-gnu-social-and-the-early-fediverse

Instead of having more users, GNU Social is now (almost?) dead. Of course it’s not just because of the above. But it wouldn’t have been set back so much without Mastodon.

Now, Mastodon is opensource, has more features and some compatible implementations. I run Pleroma myself. But why would one think Meta could not cripple them both?

Don’t know if that covers your need, but at least their angle is privacy:

https://puri.sm/products/librem-awesim/

For example:

https://farm.bot/

There are others. Plenty of small/medium businesses just don’t have the resources to develop small computers and the matching software stack. In that regards, the RPi is an appealing choice.

“Collapse” meaning what, exactly? Do you mean run out of storage from the volume of content, or that processing all the messages is too taxing?

Years back, I setup a Synapse’s server on my personal server (Yunohost). At some point, I joined the “big” Matrix room. Bad idea: RAM and CPU usage went through the roof. I had to kill the server but even that took forever as the system was struggling with the load.

But don’t just take my words for it:

https://github.com/matrix-org/synapse/issues/7339

Last comment is from less than one year ago. I was told things should be better with newer servers (Dendrite, Conduit, etc.), but I’ve not tried these yet. They’re still in development.

How does it scale differently than Matrix?

The Matrix protocol is a replication system: your server will have to process all events in the room one or more users attend(s) to. There is a benefit to this: you can’t shut down a room by shutting down any server: all the other ones are just as “primary” as the original. Drawback: your humble personal server is now on the hook.

XMPP rooms are more conventional: a room is located on one server. That’s an “old” model, but it scales.

https://www.ejabberd.im/benchmark/index.html

That’s for the host. For other attendees, it’s much lower.

I don’t think I atteld any public room out there with 3k users, so I can’t report my first hand experience, this is the best I found. But I never had to check for load issue on a small server (running Metronome and many more services).

Out of curiosity, why do you say this?

I don’t use the Fediverse the way I engage with individual people. If I want a closer relation with someone, I don’t want to be bound to yet-another-messenging system, let alone on multiple accounts

And another reason is I may not want to be bothered by people I don’t know, regardless how much I could appreciate reading and/or exchanging with them in the Fediverse.

Ignoring or declining requests from strangers can leave a lot to interpretation and then frustration. Remove the button and no one is tempted to press it the be disappointed with the outcome. Less drama.

And that’s only considering well intended people.

But these are my humble 2cents.

What I don’t like with Matrix is the load it puts on the server. It basically copies 100% of a room content to any server having one or more users registered in the room.

So if you’re on a small server, and one user decides to join a 10k+ large room, your server may collapse under the load as it tries to stay in sync with the room’s activity. This is deterrent to self-hosting or family/club/small party servers.

XMPP, on the other hand, has proven to be highly scalable, has E2EE, federation and some bridging services.

The only thing XMPP does NOT have is a single reference multiplatform client with all basic features for 2023 (1:1 chat, chat rooms, voice/video 1:1, and voice/video conference) than anyone can use without wondering if the features-set is the same as the persons you’re talking to.

And while we’re there: I’m not even sure I want a messaging account linked to any of my Fediverse accounts…