Munin feels a little old and crusty, but just works. Over 20 years old now.
XMPP lacks good clients and suffers from fragmentation of protocol standards implementation
- For Android: Conversations is excellent, also on F-Droid if you don't want to use the Google store.
- For iOS/MacOS: Siskin or iOS/MacOS: Monal.
- For Linux/Windows: Gajim or Linux: Dino.
"Protocol fragmentation" is not a valid complaint about XMPP -- it's like complaining that ActivityPub is fragmented; but that's not a problem: you use the services (Mastodon, Lemmy, Kbin, etc) built with it which suit your needs, mostly interacting with that sector of the federation (eg, Lemmy+Kbin), but get a little interoperability with other sectors as a bonus (eg, Lemmy+Mastodon).
When human shields are used, the attacking party must take into account the risk to civilians. 191 Indiscriminate or disproportionate harm to civilians remains unlawful and the civilian population can never be targeted.
So, from this I understand that every time Israel makes an accusation of "human shields", it's a direct admission of guilt of war crimes in that they are knowingly targeting civilians.
Reader mode exposes a much better headline:
Scientists testing deadly heat limits on humans show thresholds may be much lower than first thought
"Current AI models cannot forget data they were trained on, even if the data was later removed from the training data set," Han's report said.
Bullshit. You delete the entire model and start again.
Huh. Even Boeing doesn't want to be associated with Boeing:
Boeing executives have repeatedly sought to make clear that the Starliner program operates independently from the company’s other units — including the commercial aircraft division that has been at the center of scandals for years.
~623 km/h in today's units.
"South Africa, which is functioning as the legal arm of the Hamas terrorist organization [...]"
-- https://twitter.com/LiorHaiat/status/1745427037039280207 (https://archive.md/L7AwX)
There used to be a sign "helping" cyclists already on the freeway by telling them "cross here with care":
But it was obliterated by a vehicle:
Even though the company didn’t really do anything truly wrong in this case, as it’s simply users reusing passwords, they still should have been better/more proactive especially with such sensitive information
There's nothing special or new or unique or unforseen about the security requirements of 23andMe.
They absolutely failed to implement an appropriate level of security measures for their service.
Mandatory 2FA could've prevented this.
You have to trust the servers with your metadata, and that the servers have their inter-server communication locked down, but at least you can choose/operate servers.
Some clients are a bit flaky with their e2e encryption defaults or from a UI perspective it is easy to send an unencrypted message (in a new chat for example) before noticing that was how it was set.
There are a few XEPs the server needs which enable things like OMEMO, efficient mobile data/battery use, offline and multiple device deliverability, file transfers, etc. Audio/video calling has various requirements as I think xmpp only facilitates the setup of the call.