• 3 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle





  • This message is displayed in the browser because Google asked your browser to do it, and your browser got the message and put it there.

    When displaying ads, the end user experience is 100% client-side. You are using your screen and speakers to observe it. You can turn off your speakers and screen if you want, which will effectively “block” the ad.

    But that is silly. Not only do you own your screen and speakers, but you have control of what you’re browser is doing, too (if you use a respectable browser). When HTML, CSS, JavaScript, and other content is downloaded, just that happened: file downloads. After it has been downloaded, your browser then consumes it.

    When it is consumed, a lot happens, but ultimately, the code in the browser displays content. Your (respectable) browser does all of this, and will change the look depending on local fonts, accessibility options, etc. With an ad block add-on, it will also remove these ads.

    However, when ads are removed, the DOM is mutated with deleted or replaced content. It is possible for a website to then write ad block detection scripts to see if the ad contents have been removed or not. There are many ways to do this, and this screenshot is the result of one way of doing it.

    However, enter the cat-and-mouse-chase of ad block block blocks. You can block your ads, then block the ad block block like this screenshot. These types of ad block rules are less common, but many public ones are available. Check the uBlock Origin lists in the setting page. By default, only about a third of the lists are enabled, and these extra blocks are in there.

    Another avenue of determining that ads were not loaded is for the server to inspect if client-side (you) requests were made to fetch the ads. Even if this is in place, the server cannot determine if you have actually watched the ad or not. It could try to do more client-side attempts at validating that you somehow displayed it, but again, that’s client-side.

    Imagine if you were sent a letter and a pamphlet in the mail. Imagine if the letter said that you could mail them back for a free sample of their product, but only if you read the pamphlet. They would have to trust that you read it, because you are reading your mail in the privacy of your own home. However, you could opt to toss the pamphlet (like an ad blocker) and never read it. It’s your mail, your home, and your choice.


  • Synthead@lemmy.mltoLinux@lemmy.mlThe Linux experice
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    If the package manager leaves you with broken dependencies, a broken system, or a system that “doesn’t work,” then there are significant bugs in how the distro has packaged things. It happens, but seldomly.

    Package managers aren’t “hard.” There are GUIs where you can search and install packages, even. In my opinion, if you have a Linux user that has avoided learning how package managers work, then they’re skipping a core foundation of how to use their operating system.




  • Also, how are you starting it? I’m looking at the Arch package in the AUR (not your distro, but just looking), and I notice that it includes a .service file. This means that it would be started as a service, and not as a user, like you’re probably attempting to do.








  • Some printers detect when cartridges have been refilled by the user and are programmed to stop working then.

    This is absurd. I would like to hear how this benefits the consumer without attempting to talk about “quality” or something. This would be like my car not starting cause I didn’t use Shell gas.

    What’s more upsetting is that printers are client side all the way. There is nothing about them that needs to reach out to the Internet to print pages. The printer itself handles the “letting you print.” So the thing sitting on your desk, that you own, is choosing this for you.


  • I agree. That would be absurd.

    However, I don’t like not having the option of using HTTP if I want to use it. It’s okay if the webserver redirects me, but I don’t like if my browser does it when I didn’t tell it to. I might want this when doing development, port tunneling, VPN stuff, etc. In most cases, it won’t matter, but when it does, it will be a pain in the ass.



  • I disagree. While in practice, this is often the same website, it is a different protocol and a different port. It just happens to use the same DNS address. You’re explicitly giving your browser a FQDN, and it is ignoring it and doing something else.

    I hope this feature can be disabled. Google has been ignoring the W3C and has shipped proprietary, insecure features in their chromium engine for a while now, so it wouldn’t surprise me if they made it permanent 🤷