I’ve already went on on why merging communities is Bad for the Fediverse (and only really helps the big corpos that get into the Fediverse), so it’s good that the badness of that “solution” is acknowledged.

As for #2: multicommunities: I seem to recall Kbin already does that, so it should work. As for sub-issue 1, "To create a multi-community, you would have to know where each community is and add it to your list. ", well that’s what webrings are for! Let’s bring them back from the '90s. Basically get’s give the power of “static search” back to the users.

Numero 3 Electric Boogaloo: Making communities follow communities, is not much of a bad idea, but I’m wary fo the issues already mentioned in it. I’m mostly concerned also about it making it harder to maintain smaller Lemmy instances due to the extra communication overhead.

Protip: Theres no need to defederate from Threads if you never started federating with them in the first place. We know exactly who they are.

FIRST

Fam, the Teslas have been manslaughtering around for a while.

I got here wondering wth was going on, it’d be weird to hear somehow that Gimp is anti-privacy, so, well, fortunately it’s not about that.

(also,

worrying about privacy

on Windows

)

Now, IIRC, Krita does have a Windows version.

Correct me if I’m wrong:

I live in a timeline where time travel has not yet been invented. Even if someone invents it in the future and travels to the past to the party, that’d create an alternate timeline where the party is attended and civilization leaps bounds ahead in glorious post-scarcity, magical socialism fashion.

But nooooo since the timeline was forked at that point, no matter how many people do, in fact, attend the party, I’m stuck in the “strand” of the timeline when no one ever did because time travel has not been invented.

Imagine pledging to get enough money to bail out someone who can literally masturbate and squirt $44B on a whim.

Bootlickers, he doesn’t need you. Really.

10th time

only now threatens jail time

Correct me but any pregraduate law student who hasn’t been skipping on their classes could get rich by filing for the obvious bias the judges have to allow 10 contempts of court, wouldn’t they?

So they apologize for being caught, not for wrecking stuff, as usual.

As much as Germany denies it, it has been proven in the last 10 or so years that they really loved their nazi days. France seems to also love having been under nazi occupation too, and they seem to have a similar anti-environmentalist attitude.

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.