clouedoc

import type { IMailCredentials } from './credentials';
import { findAndFetchMessage } from './fetch-mail';

/**
 * Check if the credentials are working.
 * @param credentials
 * @throws if the credentials are invalid
 */
export async function mailCheckValid(credentials: IMailCredentials): Promise<void> {
	const messages = await findAndFetchMessage(credentials, ['ALL']);

clouedoc

pgbouncer: no such user

If pgbouncer is returning a no such user error, make sure that BYPASSRLS is not enabled on the user that you are trying to connect to.

I don’t exactly know why, but it won’t work.

ALTER USER myuser WITH NOBYPASSRLS

clouedoc

Weird TimescaleDB permission error

Hello there,

I've encountered this error while trying to add a TimescaleDB (Postgres) datasource to Postgres:

Pq: function time_bucket(unknown, timestamp without time zone) does not exist

There is no solution online, so I've decided to post mine here. I hope that it finds you well

clouedoc

[
        "CV",
        "ID",
        "BA",
        "CR",
        "CD",
        "BF",
        "NP",
        "SE",
        "PT",

clouedoc

FROM salrashid123/squidproxy

ENTRYPOINT [ "/apps/squid/sbin/squid" ]
CMD [ "-NsY", "-f", "/apps/squid.conf.intercept"]

# test your proxy with this command:
# curl --insecure --proxy http://<Your Proxy Host Here>:3128 https://www.lagado.com/tools/cache-test | grep "page serial number</b></td"
# the number should be the same everytime

clouedoc

import { CDPSession, Page, Target, WebWorker } from 'puppeteer';
import { PuppeteerExtraPlugin } from 'puppeteer-extra-plugin';

const blockedResources: string[] = [
  // Assets
  '*/favicon.ico',
  '.css',
  '.jpg',
  '.jpeg',
  '.png',

clouedoc

// This is a workaround for https://github.com/eslint/eslint/issues/3458
require('@rushstack/eslint-config/patch/modern-module-resolution');

var isDev = process.env.NODE_ENV === "development";

module.exports = {
	root: true,
	extends: [
		"@rushstack/eslint-config/profile/node",
		"@rushstack/eslint-config/mixins/friendly-locals",

clouedoc

Did anyone else notice that Akamai generated two canvases? One of them is large, and the other is pretty small.

The big canvas they use looks like this: https://arh.antoinevastel.com/assets/media/sneakers/anon_canvas1_footlocker.png. The small (16x16) canvas they use looks like this: https://arh.antoinevastel.com/assets/media/sneakers/anon_canvas2_footlocker.png.

My intuition is that the checksum of the small canvas will be the same on every GPU and OS. They use the first canvas for fingerprinting and the second one to check that the user did not apply noise to their canvases. (anti-canvas-fingerprinting extension will indiscriminately apply noise to all canvases)

This intuition coincides with a 2014 research paper I recently skimmed through where you can read:

clouedoc

(?m)(?:(.+?)\n(?:(?:.+?)?\n)+.+?$)|(.+?$)

# Replace with "$1$2"

clouedoc

document.querySelectorAll('.blurred-row').forEach(row => row.setAttribute('class', 'ng-star-inserted'))