Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)M
Posts
45
Comments
309
Joined
3 yr. ago

  • Why do I need to know all of this stuff, why isn’t the web safe by default?

    The answer to questions like this is often that there was no need for such safety features when the underlying technology was introduced (more examples here) and adding it later required consensus from many people and organizations who wouldn't accept something that broke their already-running systems. It's easy to criticize something when you don't understand the needs and constraints that led to it.

    (The good news is that gradual changes, over the course of years, can further improve things without being too disruptive to survive.)

    He's not wrong in principle, though: Building safe web sites is far more complicated than it should be, and relies far too much on a site to behave in the user's best interests. Especially when client-side scripts are used.

  • Haha... Maybe he keeps tabs on the fediverse?

    It doesn't work with Resist Fingerprinting mode (which hides OS settings), and doesn't have a manual toggle that I can see, but does now have a @media(prefers-color-scheme:dark) clause in its CSS. That's a step in the right direction. :)

    Thanks for the tip!

  • Please unblock challenges.cloudflare.com to proceed(grumble, unblock, reload)

    Verify you are human(click)

    ...spin...spin......spin...Verify you are human(click)

    ...spin...spin......spin...Verify you are human(click)

    ...spin...spin......spin...Verify you are human(click)

    ...spin...spin......spin...Verify you are human(click)

    ...spin...spin......spin...

  • If you want per-directory encryption, there are several options. This front-end project lists a bunch of them in its Supported Backends section.

    (Full disk encryption does have a single conventional answer: LUKS. Many distros offer to set this up at install time.)

    You're posting in a programming community, though, not a linux help community. Are you looking for a library for use in software you're writing?

  • SourceHut burns my eyes. Has Drew (or someone to whom he has delegated such things) announced a dark mode yet?

  • For multithreaded CPU-bound applications, just don’t use pure python, unless the intensive work is done in a compiled module. (Those have always been able to run without the GIL, there are a bunch of them in the standard library and other popular packages, and the API for writing custom ones is pretty good.)

    FTFY

  • Libcurl is at the foundation of almost all networking.

    That's not remotely true, but it is nevertheless outstanding work and very much deserving of recognition and support.

  • I nominate Paul Eggert and Arthur Olson before him, for the tz database, which we all depend upon whenever the time at which something happens (or did or will happen) matters.

    Edit: Tom Scott touches on the subject here.

  • Chrome is so popular that some websites only work with Chrome.

    It's the Internet Explorer problem all over again, but this time from an even more invasive company.

    The more people choosing non-Chomium browsers, the better. Keeping them popular enough that most sites have to support them is the only way to preserve what little agency people still have on the mainstream web.

  • Go get 'em, Steve!

  • Using a tool like this to hide sections of code presented for review places a lot of trust in the automation. If Mallory were to discover a blind spot in the semantic diff logic, she could slip in a small change for eventual use in an exploit, and it would never be seen by another human.

    For example, consider this part of the exploit used in the recent xz backdoor. In case you don't see the problem, here's the fix.

    Rather than hiding code from review, if a tool figured out a way to use semantic understanding to highlight code that might be overlooked by a human (and should therefore be reviewed more carefully), it could conceivably help find such things.

  • Also, when building services that are expected to send HTML email, make sure to generate a plain text version of the content and put it in the appropriate multipart section of the message. Otherwise, people reading in plain text won't see it unless they're willing to jump through hoops to do so (and there's a good chance they'll toss it in the trash instead).

    Bonus points if the plain text part is formatted well.

  • Now might be a good time to start getting familiar with Krita and/or GIMP. They will have different workflows and might not fit well in every situation, but reducing reliance on user-hostile corporate terms and closed, poorly-defined file formats is likely to be worthwhile in the long run.