• 0 Posts
  • 82 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle




  • I’m not sure about what the article is referencing, which is probably a little more exotic, but relay attacks are very common against keyless cars. Keyless cars are constantly pinging for their matching fob. A relay attack just involves a repeater antenna held outside the car that repeats the signal between the car and the fob inside the house. Since many people leave the fob near the front of the house, it works and allows thieves to enter and start the car. Canada has has a big problem with car thieves using relay attacks to then drive cars into shipping containers and then sell them overseas.







  • Gaza or the West Bank? If both, then no and yes. Israel dismantled settlements in Gaza in 2005. Unfortunately, settlements continued in the West Bank, aggravating efforts to conclude the hand off of two of the three districts there.

    Hamas is from the Gaza Strip, not the West Bank though. Gaza relations have been weird, but stabilizing with daily work travel through the border. Arguably, Hamas attacked now for fear that relations would continue to improve with Gaza, setting back their mission.





  • I suppose that’s my point though. Most of this thread, and the page linked have been asserting clear and unequivocal violation of gdpr, but that doesn’t appear to be true. It hasn’t been tested or ruled on authoritatively, and the technical mechanism makes s difference as well. There is room to equivocate.

    My own personal opinion is that I doubt the EU policy makers or courts will treat the mechanism to ensure the delivery of ads with as much skepticism as they treat tracking, fingerprinting, and other things that violate privacy. Courts and policy interpreters often think of the intent of a law, and I don’t think the intent of GDPR was to potentially undermine ad supported business.

    My goal in replying throughout the thread has been to address what feels like misinformation via misplaced certainty. I’m all for explicit consent walls, but most people in this thread don’t seem to be taking an objective look at things.



  • That is addressed in the source I linked, which is an industry groups advice to publishers on the implementation of ad block detector. They specifically say that having it listed in your ToS is a defensible strategy but could have some risk. To mitigate the risk, you can introduce either a consent banner, consent wall, or both.

    It’s an interesting read, and something I wish I’d had a few years ago in a prior role when I wrote my organizations gdpr strategy, though I’m not an expert on EU specific law.



  • That doesn’t appear to be correct.

    Executive Summary
    • Ad blocker detection is not illegal, but might, under a strict interpretation of the ePrivacy Directive be regulated and require the informed consent of users.

    • Depending on the technical implementation of ad blocker detection, such detection may be out of scope of the consent requirement of the ePrivacy Directive, or fall within an exemption to the consent requirement. But the legal situation is not very clear.

    • Publishers who use ad blocker detection should update their privacy policy to
    include use of ad blocker detection scripts.

    • Publishers may want to err on the side of caution and obtain consent for the use of ad blocker detection scripts to preempt and avoid any legal challenges.

    • Publishers could obtain consent by slightly modifying their existing compliance mechanisms for the use of cookies as the possible new consent requirement
    emanates from the same law mandating consent for the use of cookies.

    • Publishers could use two practical solutions to request and obtain consent for
    the use of ad blocker detection: a consent banner or a consent wall.
    Publishers could also make use of a combination of the two to complement
    each other.

    Source