Sometimes the food can do it too – I scratched my last nonstick pan with a silicone spatula because I ground black pepper on my eggs and caught a craggy piece just right while flipping. After being super careful for months! So irritated.

Same issues with Pop!_OS – I’m having a much better time on Nobara. But you’re making me want to try Kubuntu… still haven’t found my happiest place but I’m happy :)

Here you go, from the repo:

  const visitAd = function (ad) {
    function timeoutError(xhr) {
      return onVisitError.call(xhr, {
        type: 'timeout'
      });
    }

    const url = ad && ad.targetUrl, now = markActivity();

    // tell menu/vault we have a new attempt
    broadcast({
      what: 'adAttempt',
      ad: ad
    });

    if (xhr) {

      if (xhr.delegate.attemptedTs) {

        const elapsed = (now - xhr.delegate.attemptedTs);

        // TODO: why does this happen... a redirect?
        warn('[TRYING] Attempt to reuse xhr from ' + elapsed + " ms ago");

        if (elapsed > visitTimeout)
          timeoutError();
      }
      else {

        warn('[TRYING] Attempt to reuse xhr with no attemptedTs!!', xhr);
      }
    }

    ad.attempts++;
    ad.attemptedTs = now;

    if (!validateTarget(ad)) return deleteAd(ad);

    return sendXhr(ad);
    // return openAdInNewTab(ad);
    // return popUnderAd(ad)
  };

  const sendXhr = function (ad) {

    // if we've parsed an obfuscated target, use it
    const target = ad.parsedTargetUrl || ad.targetUrl;

    log('[TRYING] ' + adinfo(ad), ad.targetUrl);

    xhr = new XMLHttpRequest();

    try {
      xhr.open('get', target, true);
      xhr.withCredentials = true;
      xhr.delegate = ad;
      xhr.timeout = visitTimeout;
      xhr.onload = onVisitResponse;
      xhr.onerror = onVisitError;
      xhr.ontimeout = onVisitError;
      xhr.responseType = ''; // 'document'?;
      xhr.send();
    } catch (e) {
      onVisitError.call(xhr, e);
    }
  }

  const onVisitResponse = function () {

    this.onload = this.onerror = this.ontimeout = null;

    markActivity();

    const ad = this.delegate;

    if (!ad) {

      return err('Request received without Ad: ' + this.responseURL);
    }

    if (!ad.id) {

      return warn("Visit response from deleted ad! ", ad);
    }

    ad.attemptedTs = 0; // reset as visit no longer in progress

    const status = this.status || 200, html = this.responseText;

    if (failAllVisits || status < 200 || status >= 300) {
      return onVisitError.call(this, {
        status: status,
        responseText: html
      });
    }

    try {

      if (!isFacebookExternal(this, ad)) {

        updateAdOnSuccess(this, ad, parseTitle(this));
      }

    } catch (e) {

      warn(e.message);
    }

    xhr = null; // end the visit
  };

That’s pretty much it! Let me know if it doesn’t make sense, I can annotate it

Very resourceful, I love it. If you remember, I’d be interested in seeing the finished product, but either way I hope it turns out great! Nice job making the time for something like this!

That’s so cool! Is it plaster? I really like the stone lines

Betteridge’s law of headlines is an adage that states: “Any headline that ends in a question mark can be answered by the word no.”

Ban me too, please? I’d prefer to not stumble across whatever you’re hosting.

Uppies for all of you!

Put your foot down everywhere then – it’s a fallacy to think that it’s not worth it to resist data harvesting because it already gets collected “everywhere” anyway, take one step at a time to make it harder and harder. Opting out of this is just one step.

Isn’t reducing the size of the dataset worth it? I’d rather them have a picture from three years ago than a new scan every month or two.

It’s not such a binary thing as winning or losing, it’s a constantly shifting process. The only way to actually lose is by giving up – instead, consider it making it as hard as possible for your privacy to be infringed upon. Sometimes it’s more inconvenient, but what makes us such a farmable populace is our reluctance to be inconvenienced. Be good at being uncomfortable.

I refused, it went fine. I had to repeat myself because it was unexpected and dudebro wasn’t prepared, and they had to turn on the other machine and wait for it to start up, but it only delayed me like 2 minutes. The more people ask, the easier it gets.

I fucking love beans

What would be extremely rock and roll-- punk rock, even – is donating all of the proceeds from that show to pro-union efforts.

#DonateItDave, or something

The mishandling is indeed what I’m concerned about most. I now understand far better where you’re coming from, sincere thanks for taking the time to explain. Cheers

Thanks for the response! It sounds like you had access to a higher quality system than the worst, to be sure. Based on your comments I feel that you’re projecting the confidence in that system onto the broader topic of facial recognition in general; you’re looking at a good example and people here are (perhaps cynically) pointing at the worst ones. Can you offer any perspective from your career experience that might bridge the gap? Why shouldn’t we treat all facial recognition implementations as unacceptable if only the best – and presumably most expensive – ones are?

A rhetorical question aside from that: is determining one’s identity an application where anything below the unachievable success rate of 100% is acceptable?

Can you please start linking studies? I think that might actually turn the conversation in your favor. I found a NIST study (pdf link), on page 32, in the discussion portion of 4.2 “False match rates under demographic pairing”:

The results above show that false match rates for imposter pairings in likely real-world scenarios are much higher than those from measured when imposters are paired with zero-effort.

This seems to say that the false match rate gets higher and higher as the subjects are more demographically similar; the highest error rate on the heat map below that is roughly 0.02.

Something else no one here has talked about yet – no one is actively trying to get identified as someone else by facial recognition algorithms yet. This study was done on public mugshots, so no effort to fool the algorithm, and the error rates between similar demographics is atrocious.

And my opinion: Entities using facial recognition are going to choose the lowest bidder for their system unless there’s a higher security need than, say, a grocery store. So, we have to look at the weakest performing algorithms.

Yeah I got the impression it was a recoverable condition after a search found a bunch of guides for “unbricking” (Android phones). Semantics are the true enemy it seems

So then it didn’t run after the car wash – unless we’re ignoring the mandatory steps needed to get it working again, the headline is pretty accurate. Or are you considering “bricked” a permanent condition?

That’s so cute, I can’t. Thanks for paying your taxes on time.