To summarize: they had a happy life until a terrorist group took them during a massacre.
Then they lived a short horrible life in the hands of their takers, while there is a war outside where one side claim to fight to liberate them without actually negociating their release and the other claims to use them as hostages while not really negociating their release either.
And somewhat, they end up dead because let’s be real: neither side gave a f*ck about them.
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?
I’m responding to
Meaning all Israeli civilians that ever served in the IDF suddenly count as military targets.
If you do what “they” do as a way to retaliate, are you any different from “them”? We need to be better than that.
This is the wrong aporoach.
You should build a mockup site, use it to raise 2M$ for the startup behind it you just created arguing you’re about to collect personal data about the age, education level and place, curiosity, etc. with overinflated numbers on their real values.
Then you hire a bench of students, or better: launch a competition for the best “fact you were told that turned out wrong” with a 1k$ prize that you eventually give to some biz angel’s investrent adviser’s child.
Once data are acquired, claim the company is now worth 10M$ and raise that much in a new round.
Finally, sell the company for 20M$ either to a tech company that will enshitify, paywall and crater it.
You still don’t have your website, but now you’re rich and you no longer care about these things.
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"
The flowers were delivered by Doordash The victim arrived in an Uber ambulance.
The part-time doctor (student) mentioned that the hospital’s rooms are now managed by Airbnb.
250$ of tips were collected along the process, but now it’s not clear who pocketed them.
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.
Assume the communication with the app it through Internet. The car must have a 4G chip (too early to see 5G in cars, I think?). So no matter what you pay, it won’t work when 4G is retired. With marketing pushing to get new standards always faster, 4G may not last another 20years.
Anyway, bear in mind that once you subscribe, they will most likely collect detailed data about how you use the features and sell that as well…
In theory, yes, you could make a mess, and any firmware is supposed to be certified to allow the device to be used.
In practice, this has been a convenient excuse to keep a whole chip with a separate OS in every smartphone, and it is very difficult to isolate from the rest of the system (see Graphene OS efforts).
I say all firmware should be opensource. Whether you’re allowed to change them or not is a separate question… for now.
Half of the job is to fix issues with existing suff, the other half is to make working stuff more complicated and problematic (aka “upgrade”), so that we’re still paid to do the first half.
I kind of hope it’s real. Down that path at some point they’ll decide the whole Internet and all modern technologies are satanist and leave Internet for good. They can embrace the Amish lifestyle, it’s a win for the rest of us.
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.
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:
“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.
By the time countries that could have built nuclear power plants would complete them, they will have collectively burnt enough coal and gas to doom humankind.
So: indeed, the world leaders didn’t try seriously.
French here. If you learn in Belgium or Switzerland, they have “septante” and “nonante” for 70 and 90.
It’s for sure more intuitive, but you have to admit that saying “four-twenty-twelve” (non-french speakers: that’s literal translation for 92) is sooooo cool!
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…
Yep, that’s textbook big tech strategy: -Build up the hype -Get the product out there, make sure as many orgs and people start using it as possible. Make it free or sell at loss if necessary -Oh yes, we broke a few laws for this. If we don’t get a waiver, we’ll have to close the service for everyone, do you realize the impact?
That’s Facebook on privacy, Uber on workers rights, etc. Now N+1th: OpenAI on copyright.