snowflake VS easylist

If you're not distributed, use an incrementing integer.

If you're distributed, look into vector clocks[1] or snowflake[2]

[1] https://en.wikipedia.org/wiki/Vector_clock

[2] https://github.com/twitter-archive/snowflake/tree/snowflake-...

MongoDB ObjectId Time, Clocks, and the Ordering of Events in a Distributed System Snowflake

There are so many of them in big data, e.g. Kafka, Spark, Flink, Delta, Snowplow, Finagle, Deequ, CMAK, OpenWhisk, Snowflake, TheHive, TVM-VTA, etc.

Twitter built Snowflake https://github.com/twitter-archive/snowflake/tree/snowflake-2010

that being said, I have seen people acting weird about the whole thing, I don't care if you're mad at HYBE or BIGHIT for not telling him, what I care about are these people acting as if Jimin cannot deal with this or handle it himself. why they are THEY asking an explanation to be given to them? this is none of your business, he's a grown man and he can handle it himself. it's funny because even if he was to talk to someone about this, we will never know and that will be him dealing with his issue. they sit on twitter.com and try to play BTS manager and think they how BTS should be managed and HYBE needs to do things their way. they have managers for a reason and we are not the ones, I can't even believe this whole thing blew up so much.

uBlock Origin has a few 'Annoyances' lists that you can enable in the settings, e.g. Fanboy's list on https://easylist.to/

import { ScreenshotOptions } from "./schema"; import puppeteer, { Page } from "puppeteer"; import { PuppeteerBlocker } from "@cliqz/adblocker-puppeteer"; import fetch from "cross-fetch"; let blocker: PuppeteerBlocker | null = null; async function blockCookieBanners(page: Page) { if (!blocker) { blocker = await PuppeteerBlocker.fromLists(fetch, [ // the list of the cookie banners to block from the https://easylist.to/ website "https://secure.fanboy.co.nz/fanboy-cookiemonster.txt", ]); } await blocker.enableBlockingInPage(page); } export async function render( options: ScreenshotOptions ): Promise<{ url: string }> { const browser = await puppeteer.launch(); const page = await browser.newPage(); if (options.block_cookie_canners) { await blockCookieBanners(page); } await page.setViewport({ width: options.viewport_width, height: options.viewport_height, deviceScaleFactor: options.device_scale_factor, }); await page.goto(options.url); const encodedScreenshot = await page.screenshot({ type: "jpeg", encoding: "base64", fullPage: options.full_page, }); await browser.close(); return { url: `data:image/jpeg;base64,${encodedScreenshot}` }; }

uBlock Origin has a few lists for cookie banners that I always keep on [0][1]

[0] https://github.com/easylist/easylist/tree/master/easylist_co...

[1] https://github.com/AdguardTeam/AdguardFilters/tree/master/An...

I think this is now fixed (or worked around) by https://github.com/easylist/easylist/issues/17937 ?

You mean the VG Wort METIS tracking in order to participate in the German royalty scheme? From a publisher perspective that tracking is necessary, but from a user perspective it's just another example of third party tracking. Thus, it is part of some filterlists that uBlock Origin users can subscribe to, for example the EasyPrivacy list. Talking to the filterlist authors is very unlikely to resolve this: after all, it is tracking, regardless of intention.

Fixed in EasyList: https://github.com/easylist/easylist/commit/859abc79711aa69441e809a394677f6392b8c59a