Supercookie uses favicons to assign a unique identifier to website visitors. Unlike traditional tracking methods, this ID can be stored almost persistently and cannot be easily cleared by the user.
ヨナストレール
/
スーパークッキー
⚠️ ファビコンによるブラウザフィンガープリント!
Supercookie uses favicons to assign a unique identifier to website visitors.
Unlike traditional tracking methods, this ID can be stored almost persistently and cannot be easily cleared by the user.
The tracking method works even in the browser's incognito mode and is not cleared by flushing the cache, closing the browser or restarting the operating system, using a VPN or installing AdBlockers. 🍿Live demo.
約
💭 インスピレーション
Paper by Scientists at University of Illinois, Chicago: www.cs.uic.edu
This repository is for educational and demonstration purposes only!
The demo of "supercookie" as well as the publication of the source code of this repository is intended to draw attention to the problem of tracking possibilities using favicons.
This is pre-release software. While we're providing migrations between versions, changes may occur at any time, and
certain features might be missing or broken. You can follow along with
the issue…
A small library for manipulating the favicon, in particular adding alert bubbles and changing images.
トムーア
/
タイニーコン
ファビコンを操作するための小さなライブラリ。特にアラート バブルの追加と画像の変更。
タイニコン
A small library for manipulating the favicon, in particular adding alert bubbles and changing images. Tinycon gracefully falls back to a number in title approach for browsers that don't support canvas or dynamic favicons.
💻 プロジェクト一時保留
Hello! I was recently displaced from my home following a few traumatic events. I wasn't able to raise enough support and so I deleted my socials and am just going to work through this on my own.
It'll take time for me to get back into this project, but it's still very functional. Here are some links:
(WIP): This is an enterprise scale advanced microservice pattern with GraphQL API and GRPC Microservices, based on Domain (DDD) using the command query responsibility segregation (CQRS) design pattern.
Want to ask Rex Isaac Raphael questions, join the slack channel :)
説明
This should be the go to backend base for your next scalable project. This is a proof of concept project designed to be extremely slim and scalable, with distributed data request and process handling, built from the ground up for production use. It comes with Multi-Tenancy SaaS support, following different multi-tenancy database strategy as well as different resolver patterns
to identify your tenants. The goal is to give your next big project that extra leap to awesomeness. To get started read the instructions below. With support for both Event Store and NATS Streaming for event streaming and Kafka comming soon.