1. 2

    Seems like one could have some fun mapping these proposed tribes to other archetypes. Here’s an example :

    applied mathematician -> priest
    hacker -> warrior
    maker -> blacksmith
    
    1. 12

      My personal experience is quite the opposite.

      I’m very happy with NoScript, only allowing a few domains I visit regularly, but not their third-party trackers.

      It’s probable I’m not blocking 100% of the crap, but I’m blocking 90-95% which definitely makes me happy.

      If a website doesn’t work with noscript, I can decide to either enable js temporarily, or just close the tab and don’t visit it.

      Overall, I always recommend tech people to browse with noscript by default.

      1. 7

        I take the same approach and also have a good time. A side effect of doing this is a better understanding of the UX and advertising surveillance used by sites I visit, and the variation in how tightly it’s integrated. Mostly, enabling JS only for the current domain allows sufficient functionality, but not always.

        1. 6

          It’s the act of constantly determining what to enable and block that burned into my time. For example, try visiting stackoverflow.com or even nativescript.org. The latter has naked Cloudfront URNs that I can’t tell are actually legit for NativeScript

          1. 1

            Stackoverflow works out of the box for me with uMatrix. It blocks some JavaScript (ajax.googleapis.com and cdn.sstatic.com), but with no immediate ill effects and easy to unblock selectively.

            Nativescript is a mess however, it seems to need that Cloudfront JS to even show its menus. (And for whatever reason uMatrix doesn’t allow easily whitelisting all of cloudfront for nativescript.)

            1. 1

              Stackoverflow’s functionality (upvoting and submitting comments) are drastically reduced (upvoting doesn’t work despite them giving the arrows a tab-index, lack of use of native form validation restrictions and semi-broken interface for the composer).

          2. 5

            Same here. I use qutebrowser, which has a 3-key shortcut combo, tsh, which stands for toggle script (for) host.

            Most of the time, I see little value in enabling JS in a site that doesn’t load without it.

            If there is an exception, it only takes 3 keys and a couple seconds’ load time to enable it for that particular domain.

            I also trained my parents (mid-50s) and a few other non-tech people on how to use NoScript effectively to speed up their browsing, and they now use it daily.

            Anyone reasonably technically-minded can do it with just a few habit changes. If you don’t care, that’s a different story.

            If you consider wasted network, wasted CPU, wasted user time, tracking and surveillance, the impact of advertising, and not to mention exploit-malware infections via the biggest, majorest websites and their ad networks, you’ve got to be an ignoramus to not disable JS.

            The only downside is that poorly designed websites with content of questionable value will not work anymore.

          1. 2

            Have you considered breaking the IPFS types and API glue out as a separate package? That would be really useful!