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.

  • 0 Posts
  • 62 Comments
Joined 11 months ago
cake
Cake day: July 26th, 2023

help-circle

  • Yeah I just checked Atkinson Hyperlegible and, at least the version I can access (the one on Github) lacks entire Latin and compatible character ranges, as well as having a substantially limited math symbols set (only two greek letters show, for example).

    The weird thing is, if I understand how fonts correctly, that shouldn’t have been an issue. The font doesn’t register those missing characters, so your browser should have known to fallback to a default typeface for the missing characters. It’d be weird if you have none of the many compatible fonts (not even, say, Times New Roman).








  • 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.


  • 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.

  • Because I left Windows precisely to avoid the kind of shittery that systemd is doing.

    It’s absolutely no coincidence that the people who have developed the stuff that’s brought the most degradation to Linux - systemd, PulseAudio, Gnome’s “user has no right to themes” attitude - all come from a Microsoft background or explicitly work for Microsoft.

    I’d have far less of a problem if systemd was split into more practical, actually independent things that actually worked and distros didn’t buy their snake oil so easily. But for the time being, to me, the systemd experience is pretty much like the PulseAudio experience, what with the whole “waiting 120 seconds for a network interface to activate that it’s not going to because it’s the damn ethernet port and I’m on the road so the cable is not connected, stupid letter-potter dipshit”.




  • While I like it conceptually, the two times I tried to install it I felt it was far too opinionated for me to get it to work correctly, like other software “bundles” of its kind that want to take control of the entire process of setting up ports, networking, storage, certificates etc…, instead of just hanging down from stuff that I have already prepared for it (like my own domain with my own cert).

    Like, as a piece of software it’s something I’d absolutely use… if someone else sets everything up for me.



  • The problem is that no browser can allow you to escape the horror that is web standards & practices that have been developed over decades […] practically the entire web is reliant on JavaScript, […]

    I’ve been saying it for a while: continuing to play catch is a losing move for Mozilla or for any independent browser maker.

    The real move, is to switch to or at least integrate an alternate internet, something that uses a protocol that is simpler and more limited by design - just get rid of Javascript (or of “remote execution”, really) and you instantly get a much leaner, much securer internet design.

    I’ve heard pretty good things about the Gemini protocol, but IMHO they went too far too extremist into the “text internet” philosophy, and as a result is a raw downgrade from Gopher. Gopher could actually be a good option.


  • 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.