Would it be for giving credit it to the Tweeter?

Tensor tympani is the muscle

I mean it’s on you to manage boxing and unboxing in your projects

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

from * import *

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

I think the distinction here is a Harris presidency would at least pretend to if not actually put effort toward resolving the conflict with less bloodshed because some of the Democrat base wants that, even if it’s only symbolic and maintains the status quo and of Israel as a “strategic partner/asset”. Blinken was just on NPR explaining where their efforts have been directed (surrounded by non-answers, take it as you will), not taking into account how effective they were. We can fully expect a Trump admin to encourage Bibi’s efforts at rejecting a two-state solution or any kind of Palestinian sovereignty, and make it even harder to end the conflict in the future because Bibi wants to drag out the suffering as long as possible because that’s a key reason he’s in power. This is how I interpret it, and I believe any kind of equivalency between the two is overly cynical, which you can feel free to disagree with. If Trump’s admin somehow has a part in ending the conflict, I’d be surprised if any Palestinians make it out on the other side, and they’ll tout that as a win.

sudo is spoken soo-doo in my house. Where I live alone.

I do, especially in VARCHAR as vare-care where everyone else is on the varr-carr train.

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

Right – all privacy-positive methods to employ, but not helpful for fingerprinting. In fact, some things can make you more susceptible to fingerprinting because they make you more unique (like using a custom OS). It’s all about your browser and what it chooses to send with HTTP requests, how it responds to queries for you device/browser specs (via Javacript). Your OS, system architecture, hardware details, browser type and plugins, etc combine to make a very unique profile tied to your device. It’s especially nefarious because all those bits are cross-referenced over all accounts and devices to make a global profile on you. Even if you’ve never used Facebook, you probably have a shadow profile. If you’ve ever logged into the same service or website account on your de-Googled GrapheneOS device as another machine that does have Google services tracking, then your new device is likely already tied to your identity.

Try this with different browsers – it tests the uniqueness of your device.

Pretty sure Graphene doesn’t do much about fingerprinting on its own, it’s nearly entirely up to the browser. They mention some of their plans to address that with Vanadium, but make no claims as to how effective it is now (at least on the features page).

The italics are a nice hint. Good Poe’s Law submission.

But following the surface of a sphere causes you to constantly change direction

A fellow opposum!

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.