• 18 Posts
  • 53 Comments
Joined 10 months ago
cake
Cake day: February 10th, 2024

help-circle

  • I would get 12mm screws of the same thread pitch (M2 is common) and file 0.5mm off the ends.

    If you don’t want to file them by hand, you could ask someone with access to a grinder for help. They could probably do it in a few seconds if the screws are not stainless steel. Your local bicycle shop might have one, since this is a fairly common operation on spokes.


  • This article mentions using Global Privacy Control as a replacement for Do Not Track, but doesn’t bother to explain what GPC does. Its adjacent article incorrectly claims that GPC uses the DNT: 1 header field, fails to explain further, and links to a Mozilla page that doesn’t explain it, either.

    Even the GPC web site fails here, offering several pages of vague, abstract fluff about their intentions and a useless document full of marketing industry acronyms, without anything substantial about how it works. The single mention of a spec fails to state where to find it. The closest it comes is a tangential sentence containing a broken github.io link.

    Finally, and only because I happen to know github.io’s URL format, I was able to guess my way to an organization page, and from there to a project page, which has a README file containing a footnote linking to the proposed spec:

    https://w3c.github.io/gpc/

    Geez… it’s as though the people involved don’t want anyone to know how this proposed safeguard is supposed to work.

    After reading it, it looks like these are the main differences in Global Privacy Control vs. Do Not Track:

    • Replaces the DNT: 1 header field with Sec-GPC: 1.
    • Adds a javascript property to indicate the same thing.
    • Does not honor preference changes after the first navigation to a site. (Having changes respected apparently requires clearing site data from the browser and reloading. A helpful browser might prompt the user to do this.)
    • Defines a way for sites to indicate that they are aware of GPC (but does not require them to honor it).
    • Expresses a wish that your data not be shared, but says nothing about it being collected.
    • May be considered legally binding in some jurisdictions. It’s not clear whether the few that currently recognize it will enforce it in any meaningful way.













  • So most software packages are at least a little out of date because they only put the most stable and tested versions of software in their default repos.

    And for many people, this is a good thing. By favoring reliability, Debian Stable provides the most low-maintenance experience of any distro I’ve ever used. (And I’ve been using them for a long time.)

    The packaged software is generally up to date when a new Debian release lands. It’s a year or two between releases, but that’s fine, because the vast majority of software already had the features I needed, and I’m not addicted to watching version numbers rise or fiddling about with UI changes that some developers like to make every month. Security updates do come between releases, and the two or three packages that sometimes warrant a faster update cycle are easy enough to add if needed.







  • Neither isolates everything. Both have some isolation features. The features enabled by default vary from package to package, so you would have to look at the permissions on each package to find out.

    For a bit more isolation than a flatpak/snap, I suggest creating a separate user account for running chromium (or any other moderately nosy software). Note that linux lets you log in to two accounts at the same time, each with its own desktop, and switch between them. Check out your desktop environment’s “switch user” function.

    For even more isolation, you could run chromium in a hypervisor-based virtual machine.