Kind of funny: When Wikipedia was new, people often said that you couldn’t trust information on it because anyone could have written it, even if they were unqualified, biased, or deliberately deceptive. I guess that’s still true today, but with the advent of automated misinformation generators, the Wiki almost seems authoritative in comparison.

Bar Keepers Friend:

According to the February 26, 2020 Safety data sheet (SDS), Bar Keepers Friend Cleanser contains:

• 85–94% glass oxide (CAS 65997-17-3),
• 5–10% oxalic acid (CAS 144-62-7), and
• 1–5% benzene sulfonic acid, mono C10–16 derivatives, sodium salt (CAS 68081-81-2).

Bon Ami:

The product called “original” contains only feldspar. For other products, the Bon Ami website lists the following as main ingredients: feldspar, limestone, water, baking soda, citric acid, corn alcohol, epsom salts, essential oils, and xanthan gum.

That’s obvious and goes without saying,

Even if you think so, I hope you will consider revising your earlier comment. As written, it is incorrect, leading uninformed readers to believe something that simply is not true.

Edit: In my experience, license terms are seldom obvious, and never go without saying.

if you change LGPL code you’re required to redistribute its source.

No, you can change LGPL code all you want without distributing the source, so long as you don’t convey it (either in source or non-source form) to any other parties. The point is to guarantee that anyone receiving the code in any form has the same freedoms that you had when receiving it.

There are a lot of misconceptions floating around regarding these licenses; it’s really worth reading and trying to understand them even if you’re not a lawyer. The FAQ might help:

https://www.gnu.org/licenses/gpl-faq.html

https://www.gnu.org/licenses/lgpl-3.0.html

https://www.gnu.org/licenses/gpl-3.0.html

Unfortunately, it’s not that simple, because attacks often involve “exploit chains”. In this case, an attacker would use a different vulnerability to gain code execution capability, and then use that capability to exploit this vulnerability.

Update your systems, folks.

Screen size: 5.8"
Device size: 6.8"
CPU/SoC: unknown

Parent company:
Xinruizhi (Shenzhen) Industrial Co., Ltd.
https://www.xinruizhi-china.com/pages/about-us

Problems like those are unavoidable even on today’s Signal, because the service depends on internet peering relationships, internet service providers, mobile network operators, cell tower reception and backhaul, etc. Oh, and Amazon.

You usually don’t notice them because when any of those components develops problems too often, affected users tend to get annoyed and switch to a more reliable one. (Also because you don’t expect to receive messages from as many people or as often as you do on Lemmy, so short outages are less likely to affect you.)

All of this would still be true in a distributed Signal, except that users could switch away from Amazon as well. Meanwhile, everyone not using Amazon would still be chatting during an Amazon outage.

We’re not talking about a distributed app, but a distributed service.

Email.
The web.
The entire internet.
The postal service.
The telephone network.

But also prone to problems stemming from that same decentralization.

Exactly what problems do you have in mind?

There is no reason to assume that a distributed incarnation of Signal would have the same design as ActivityPub or Lemmy.

“The question isn’t ‘why does Signal use AWS?’” Whittaker writes. “It’s to look at the infrastructural requirements of any global, real-time, mass comms platform and ask how it is that we got to a place where there’s no realistic alternative to AWS and the other hyperscalers.”

To me, this reads as sophistry.

What happened here is a predictable result of Signal’s design. They chose to build a centralized messaging system. This made things significantly easier for them than a distributed design would have been, but it comes with drawbacks. Having single point of failure is one of them. (In this case, that single point is Amazon.)

Trying to direct the public’s focus onto cloud providers instead of acknowledging this fundamental shortcoming in their design is, frankly, disingenuous. Especially coming from someone in Whittaker’s position.

While we’re at it, let’s acknowledge that centralized design in messaging systems is problematic not just because of (un)reliability, as seen here. It also creates a single point of attack for any entity seeking to restrict, shut down, or track people’s communications. End-to-end encryption cannot solve those problems.

Updating the system swaps out the old OS image for the new one; it’s both fast and safe. And you can keep around the old OS image (three of them, in fact) and easily roll back if you have a problem.

So an entire OS image is written to the SSD whenever something within it is updated?

I hope they employ de-duplication, or some other way to avoid wasting NAND cell life.

I prefer KDE Plasma, too. Fortunately, just about every desktop distro has it available even if GNOME or something else is the default. Find out what package to install. (On Debian-based distros, it’s probably kde-plasma-desktop.) Install it, log out, and look for a session selector on the login screen. Change it to Plasma before logging in again.

If the same game problems reappear when you’re on a different distro, you might want to describe them in detail on a Linux gaming forum. Someone there might be familiar with how to fix them.

!linux_gaming@lemmy.world

Welcome to the neighborhood!

Thank you for the confirmation!

Related:

https://www.collabora.com/news-and-blog/news-and-events/pipewire-bluetooth-support-status-update.html

I think this could be done by running a Bluetooth Hands-Free Protocol (HFP) implementation on the linux desktop machine, so a phone would see it as a wireless headset. This project from a decade ago seems to confirm that it is possible:

https://nohands.sourceforge.net/index.html

https://github.com/heinervdm/nohands

That project looks unmaintained. If I were to try something like it today, I might start by asking around in PipeWire forums to see if anyone had tried such a thing.

(FYI, KDE Connect is very useful, but it doesn’t do phone calls.)

Good luck! If you figure it out, I hope you’ll post about it so we can all learn from your experience.

there no longer is an overarching standards body who makes the decision

The creators of the FHS were never an overarching standards body. Despite its name, the FHS is more a set of conventions than a standard.

The closest standard that comes to mind is POSIX.

https://pubs.opengroup.org/onlinepubs/9799919799/

As far as I can tell, advertising.

BEST most strongly marketed

I’m willing to assume Zorin is a solid distro, and I suppose some Windows expats might enjoy a Gtk-based desktop, but experience has shown that some are more at home with KDE Plasma.

And the blowfish represents OpenBSD, not BSD in general.

These mascots make sense once you understand the projects from which they come.

Wikipedia says its community edition is AGPL licensed.