/h/meta

MayflyAlt-98 Your/Grace Self-taught hypebeast 1mo ago (image post) 479 thread views #308084

FEATURE REQUEST : The Sharty's datamining is so good it tags people who have Groomercord running in the backround.

Block /h/meta

Jump in the discussion.

No email address required.

Gibberish gibb/erish :marseyautism:

1mo ago #7165211 Edited 1mo ago

!codecels Unironically how would this work? I didn't think you could pull that kind of data from a browser.

Edit - found a possible solution from back in 2015 for mobile browsers to see if the app is installed. Are groomercordcels just phoneposters?

23 Context

gerudo p/n Gibberish 1mo ago #7165219

Dns caching. Pick one of the dicords domains, do a dns request for it, see how long the request takes. If it's near instant, then it was probably resolved locally, meaning it was cached locally. The ttl for those is probably around 10 minutes, so that means it was accessed <10 mins ago. If you have groomercord open, it's making a request every second, so the domain will be cached.

21 Context

cyberdick pedda/modda Dead name deez nutz ya queer. 🍒🍆 gerudo 1mo ago #7165234

19 Context

AnnoyinTheGoyim oy/vey :squirreljak:

JUSTICE 4 PEANUT :squirreljak2:

gerudo 1mo ago #7165252

Timing attacks don't really work in browser? The clock isn't accurate enough.

7 Context

gerudo p/n AnnoyinTheGoyim 1mo ago #7165263

Your router is milliseconds away, your local cache is microseconds away. The browser clock is absolutely precise enough to measure that difference.

9 Context

AnnoyinTheGoyim oy/vey :squirreljak:

JUSTICE 4 PEANUT :squirreljak2:

gerudo 1mo ago #7165282

No, the browser clock doesn't give you access to that precision. They do this on purpose to prevent timing attacks.

10 Context

gerudo p/n AnnoyinTheGoyim 1mo ago #7165338

https://developer.mozilla.org/en-US/docs/Web/API/Performance_API/High_precision_timing#reduced_precision

6 Context

AnnoyinTheGoyim oy/vey :squirreljak:

JUSTICE 4 PEANUT :squirreljak2:

gerudo 1mo ago #7165359

That's what I said? But in any case, you can't measure the DNS resolution time in the browser, at least not for cross origin requests.

7 Context

gerudo p/n AnnoyinTheGoyim 1mo ago #7165901

It's like 100ms different between a request with a clean cache and a second request. Go try it.

4 Context

AnnoyinTheGoyim oy/vey :squirreljak:

JUSTICE 4 PEANUT :squirreljak2:

gerudo 1mo ago #7166055

You can't reliably measure DNS resolution time from a round trip to their server. Why don't you actually try it.

3 Context

Zuzie zoz/zle gerudo 1mo ago #7165336

How would you detect the difference in time though? Your browser isn't making DNS requests in a way that your webpage will see.

6 Context

Deleted by author

Healthy who/whom gerudo 1mo ago #7165420

Webpages can initiate DNS requests?

10 Context

goderator200 we/are/god Healthy 1mo ago #7165744 Edited 1mo ago

googlegpt says no, but u can measure the perf:

const url = 'https://www.example.com';

fetch(url)
  .then(response => {
    // Handle the response
  })
  .catch(error => {
    // Handle the error
  });

const observer = new PerformanceObserver(list => {
  const entries = list.getEntries();

  for (const entry of entries) {
    if (entry.name === url) {
      const dnsLookupTime = entry.domainLookupEnd - entry.domainLookupStart;
      console.log('DNS lookup time:', dnsLookupTime, 'ms');
    }
  }
});

observer.observe({ entryTypes: ['resource'] });

fuck black lives matter