How about block com.google.android.*?

Back in the time when I disliked it and, to a lesser extent, AppArmor, the reason was pretty simple:

It forces services to lie to me / It gets in the way of software doing what I tell it to do.

The examples would be rather simple. Need to spin up a second instance of a database server, sure, just set up the given config file with datadir=/mount/point/second/disk/var/lib/database. Should work... Nope. Database errors out despite the directory existing and being writable and all permissions being right. Insists it's "file permissions". Try to look around, to no end. Then it turns out there is some secret NSA Cabal infiltrated in my server already that... for some weird reason, forces databases to be installed on /var/lib even though when that is almost full and I mounted a second disk to have more room. And thus the service lies to me, says file permissions, well I checked them several times and they were alright.

Stupid NSA cabal thing stupidly getting in the way of configuring things and adding more entrypoints you have to edit and services you have to configure just to start up a program. I want to start a database, not set up a DEFCON 1 line! Those days I was beginning to miss SQLite already...

Similar issues I had with webservers, network share servers, joysticks and gamepads, and even audio devices. Never got a clear idea of what it was, software says something like "permission error" or "not a device file" but I checked and those are alright. A long sigh, remember than when you install a new computer you have to disable SELinux and AppArmor and reboot, boom, done, everything magically works.

Fortunately things have improved a long way since, but back in the day, they were one of the most grating obstacles to me for getting friends, let alone clients, to adopt Linux.

I knew that lemmy having the issue of instance identity being tied to DNS was going to eventually bite it in the ass.

It if weren't for that, it'd be as easy as migrating the instance to a different jurisdiction. Which, speaking of, is a whack-a-mole game; what we need is to set up shop in some sort of international waters jurisdiction or something that has enough soverengity and amicability that assures say the UK can't legally threaten it anymore than they can threaten a random online-delivery donut shop in Laos.

This is one of the reasons I use schroot + debootstrap. Got a Debian chroot and a Ubuntu chroot so that I can manhandle them rough installing PPAs and packages and stuff, without seriously endangering my main install.

no ties to my privilege

it's an AI startup

$185 million

Something does not compute, in a Microslop sort of way.

endless feed

to fight algorithm addiction

endless

feed

to fight algorithm addiction

Uuuuuh that's not the way to fight an addiction, right? Who is this person working for, exactly?

Not really conductive as long as most funds are siphoned by the C-suite ranks. Get rid of the C-fat first, maybe even turn Mozilla into a co-op, then have the People fund it.

Oh if only Proton could learn this power!

This definitively was not in my 2024 Bingo card:

Republicans masking

Quick! Someone add it to Open Slopware!

What I'm hearing here is

Proposal to add current Fediverse symbol to Unicode

Storm in a teacup, as tends to be the norm on the internet.

Not only this is nothing new and nothing unexpected to happen in Sid of all places, but it's also something that helps bring keepassxc more in line with packaging guidelines on Debian. They already have lots of packages, both of the mutually-exclusive kind and of the complementary kind, with "foo-full", "foo-minimal", "foo-data" etc naming. p7zip and nginx of all things are quite interesting examples.

Plus, the author of the post sensationalizes the title to brigade the issue.

All that said:

• If the maintainer wishes to do this, "only" having two packages is a half-assed measure and that causes more issues in the long term. I'd expect three packages: keepassxc-minimal, keepassxc-full and the retained name keepassxc as a virtual package name.
• Furthermore, a direct upgrade path should go from (previous) keepassxc to (proposed) keepassxc-full.
• I don't know enough of KeePassXC to know if something like keepassxc-data would be needed. Are there potential cases where one would want to switch between "-full" and "-minimal" or viceversa without the system seeing a software uninstallation in the meantime?
• The "crap" rationale is definitively something we all can do without, but given how people tend to brigade developers who try to do things, I can completely understand and support raising shields and looking defensive because some damage is already going to be done.
• Most responses are right in that the right place to discuss this is in the opened Debian bug report. The entire point is to see Debian (not KeepassXC) handle this before things get to Next Stable.

Well, what’s stopping someone else from adopting TomHanks@Lemm.ee?

There's over 1400 people solely in the US named Tom Hanks. Tom Hanks The Celebrity does not get patent rights or trademarks or copyrights on the name.

Wanna know which is the Tom Hanks The Celebrity? Check if their profile is authenticated against their personal website, à-la-Mastodon.

"The research is published in a git repository with every source embedded. It does not depend on Reddit's infrastructure to survive."

proceeds to post on Microslop's Github

Being compared to Hitler is not going to disturb him that much, I feel. He loves it.

Which means, add to your repertorie! Like, you can call him "Mr. Krasnov" as well.

So, since this is a clear and flagrant violation of law, at least one prosecutor somewhere is going to sign an arrest warrant.

Right????

So, Luigi.

This can't be C++. Not enough stacks of unneeded template names, and the function names are not mangled beyond recognition.

I don't get how people get hung on choosing a server when people have been chosing a starter Pokémon since 1998 without any major issues. And you get just about the "same" amount of practical info.

Really, what tiktok does to a generation...

...backup servers? 👀