lambalicious

@lambalicious@lemmy.sdf.org

I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

lambalicious,

And no, it wasn’t just the favicons feature that was removed (which like … is that really such a big privacy issue that you need to remove it from the binary?)

Fetching a favicon means raising a network connection with a predictable endpoint. That’s already three concerns (four on the modern internet) to handle security-wise, and it’s absolutely an unneeded feature. Favicons could just be shipped on something like keepassxc-data or keepassxc-contrib to handle locally, no need to raise a network call.

lambalicious,

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.
lambalicious,

People who are looking to start a SE alternative but start with the idea of importing the original SE data dumps are already Doing It Wrong. Much of the issue that has led to the desire to fork SE comes due to the license of the posts and content, which lacks the NC (NonCommercial) component of Creative Commons. Without that component, any attempt to make a Fediverse alternative just ends up in Yet Another Endpoint that can be freely siphoned for data by corporations, for AIs, etc.

lambalicious,

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?

lambalicious,

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.

lambalicious,

So, you want people to miss out on cat pictures because your feelings were hurt?

lambalicious,

So basically you are looking for a Linux distro without an open source license? And probably without a license at all…?

lambalicious,

Putting a cost on software is adding a restriction, thus making it less free (as in freedom).

Don’t confuse “free from cost” with “free from restrictions”.

Writing software costs costs - be them time, money, evne mental health as we have often seen because of too many entitled people in these communities. Putting a price on the software means valuing it for what it is, and does not incur in any additional restriction on the usage of the software.

All that said, I think the cost of free software, at least when it comes to infrastructure software, is something that shouldn’t be necessary for the end user to pay. Similar to how we pay taxes, instead of paying for the installation of semaphores on our streets directly.

If I were to design any such global system, it would be eg.: distro maintainers who would pay a maintenance cost to the developers of the dependencies they ship. Probably in the form of a funding pool that is distributed across projects prioritizing those that 1.- have ethics and development practices more similar to the distro’s and 2.- are in need of more immediate attention for solving security or usability bugs.

Furthermore, national-level funds for this would be collected via a taxation system managed by an academic office or other such entity and taken in a measure scaled according to the nation’s average technological “estate” (after all, developing and maintaining a more complex system requires more cares and attentions).

lambalicious,

Perhaps we should take the clue and - if we also see clues of Mozilla enshittifying - switch globally to an easier internet that’s also easier to program for. Something like Gemini (the post-Gopher thingy, not Google’s latest fad) for example, where I take it maintaining a browser is nowhere near the same order of magnitude as complex.

lambalicious,

FIRST

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

lambalicious,

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.

lambalicious,

And the fedi is full of that.

[citation needed]

lambalicious,

Finally, Kissinger is dead — but for the karmic balance, even SMT gets enshittified.

lambalicious,

I don’t get the issue with “maintaining Xorg”. Like, I get that it has a “cost”, I just don’t understand why that cost would be an issue since it’s basically fixed, marginal cost (and has been since like 2015): the software is already mature, so it’s unlikely to see relevant changes, or even minor changes (if that’s what we want to mean with “dead”). That means, it can be affixed to a specific toolkit and environment to build (if this isn’t being done already - which any mature project like RedHat should be!) basically guaranteeing it’ll build forever. You can just set a virtual button or a yearly crontab to do it. Fixed, marginal cost.

Contrasted to that, what Wayland is doing is kinda a representation of the worst ways of capitalism: centralize the profits, socialize the costs and the externalities (redesign, recode, rebuild), and blame society (the Linux communities) for it, all for a variable cost that is unbounded in time and space because you never know what’s gonna cost a small project like a text editor to reimplement the entire desktop stack “just” for Wayland.

lambalicious,

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.

Unity issue an apology on Twitter for "confusion and angst" over the runtime fee policy. (nitter.net)

We have heard you. We apologize for the confusion and angst the runtime fee policy we announced on Tuesday caused. We are listening, talking to our team members, community, customers, and partners, and will be making changes to the policy. We will share an update in a couple of days. Thank you for your honest and critical...

lambalicious,

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

lambalicious,

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.

lambalicious,

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.

lambalicious,

May I introduce you to the world of insurance companies?

lambalicious,

Poachers don’t do what they do because they’re greedy and hate animals, they do it because they’re poor and have often no other choice but to risk their lives to make a living,

Well, they’re risking their lives, they’re losing them in the gamble. No one owes you winning a gamble.

This is a systematic problem perpetually reinforced by the actual people we should be shooting: the millionaires who hire the poachers

Not saying we don’t, I’m all in for shooting a millionaire myself; but that doesn’t detract from still needing to kill the poachers: we can’t leave the reservoires and wild habitats unguarded merely to kill one or two twitter twats, so the job of millionaire killer we have to give to someone else.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • rosin
  • thenastyranch
  • ethstaker
  • DreamBathrooms
  • osvaldo12
  • magazineikmin
  • tacticalgear
  • Youngstown
  • everett
  • mdbf
  • slotface
  • ngwrru68w68
  • kavyap
  • provamag3
  • Durango
  • InstantRegret
  • GTA5RPClips
  • tester
  • cubers
  • cisconetworking
  • normalnudes
  • khanakhh
  • modclub
  • anitta
  • Leos
  • megavids
  • lostlight
  • All magazines