LLM answer:

- Tracking Pixels and Web Beacons
- Email-Open Tracking
- Email Link-Click Tracking
- Advertising Impression Tracking
- Conversion Tracking
- Social-Media Pixels
- Analytics Tags and Tag Managers

- IP Address and Network Tracking
- IP-Based Geolocation
- ISP, ASN, and Organization Identification
- Household and Network-Level Matching
- VPN, Proxy, and Tor Detection
- Network Reputation and Fraud Scoring

- URL and Referral Tracking
- UTM Parameter Tracking
- Advertising Click-ID Tracking
- Affiliate and Referral-ID Tracking
- Email Campaign-ID Tracking
- Link Decoration
- Redirect-Chain Tracking
- Cross-Site Identifier Propagation
- HTTP Referer Header Tracking

- HTTP Header and Cache Tracking
- User-Agent Tracking
- Client Hints Tracking
- Accept-Language Tracking
- ETag Tracking
- Cache-Control and Last-Modified Tracking

- Browser Storage Tracking
- First-Party Cookies
- Third-Party Cookies
- LocalStorage and SessionStorage Tracking
- IndexedDB Tracking
- Cache Storage Tracking
- Shared Storage Tracking
- Service-Worker Storage Tracking
- Evercookies and Identifier Respawning
- Supercookies
- HSTS Supercookies
- Favicon Cache Tracking
- TLS Session-Resumption Tracking

- Browser Fingerprinting
- Browser, Version, and Operating-System Fingerprinting
- Screen, Viewport, Color-Depth, and Device-Pixel-Ratio Fingerprinting
- Time-Zone, Language, Locale, and Keyboard-Layout Fingerprinting
- Installed-Font and Font-Rendering Fingerprinting
- Canvas Fingerprinting
- WebGL and WebGPU Fingerprinting
- AudioContext Fingerprinting
- GPU and Graphics-Driver Fingerprinting
- CPU Core, Device-Memory, and Hardware-Concurrency Fingerprinting
- Touchscreen, Input, and Device-Capability Fingerprinting
- Camera, Microphone, and Media-Device Fingerprinting
- Browser Extension, Plugin, MIME-Type, and PDF-Viewer Fingerprinting
- CSS Feature and Media-Query Fingerprinting
- Browser API Availability Fingerprinting
- WebRTC and Local-IP Exposure
- Network Information API Fingerprinting
- TLS, JA3, and JA4 Fingerprinting
- HTTP/2 and HTTP/3 Protocol Fingerprinting
- DNS Resolver Fingerprinting
- Clock-Skew and Performance-Timing Fingerprinting
- Sensor Fingerprinting
- Motion, Orientation, and Ambient-Light Sensor Fingerprinting
- Speech-Synthesis Voice Fingerprinting
- Emoji and Text-Rendering Fingerprinting
- Math, Floating-Point, Error, and Exception Fingerprinting
- Browser Automation and Bot-Detection Fingerprinting
- Combined and Probabilistic Fingerprinting

- Account and Login-State Tracking
- Logged-In Account Tracking
- Login-State Detection
- Single Sign-On Tracking
- OAuth and Social-Login Tracking
- Embedded Social-Widget Tracking
- Account-Recovery Identifier Matching

- Cross-Device and Identity-Graph Tracking
- Login-Based Device Linking
- Hashed Email and Phone-Number Matching
- Probabilistic Device Matching
- Data-Broker Identity Resolution
- Offline-to-Online Data Matching
- CRM and Customer-Data Matching

- Server-Side Tracking
- Server-Side Analytics
- Server-Side Tag Management
- Server-to-Server Event Tracking
- Advertising Conversion APIs
- Purchase, Order, and Lead-Event Sharing

- Behavioral Analytics and Session Replay
- Mouse-Movement Tracking
- Scroll-Depth Tracking
- Click and Hover Tracking
- Keystroke and Form-Interaction Tracking
- Heatmap Tracking
- Rage-Click Detection
- Dwell-Time and Engagement Tracking
- Form-Abandonment Tracking

- Push-Notification Tracking
- Web Push Subscription Identifiers
- Mobile Push Tokens
- Notification Engagement Tracking

- Mobile-App Tracking
- Mobile Advertising IDs
- App Instance and SDK Identifiers
- App-Install Attribution
- Deep-Link Tracking
- Mobile Device Fingerprinting
- Mobile Location Tracking

- Location Tracking
- GPS Location
- Wi-Fi Network Location
- Bluetooth Beacon Location
- Cell-Tower Location
- Nearby Device and Network Discovery

- Embedded Third-Party Content Tracking
- Embedded Video Tracking
- Embedded Map Tracking
- Comment-Widget Tracking
- Payment-Widget Tracking
- CAPTCHA and Anti-Bot Widget Tracking
- Third-Party JavaScript Tracking

- DNS and Domain Cloaking
- CNAME Cloaking
- First-Party Subdomain Tracking
- Domain Alias Tracking
- DNS Query Tracking
- DNS Prefetch Tracking

- Advertising and Attribution Tracking
- Real-Time Bidding Tracking
- Ad-Exchange and Demand-Side Platform Identifiers
- Retargeting and Remarketing
- Frequency-Capping Identifiers
- View-Through Attribution
- Multi-Touch Attribution

shoutout to yggdrasil
https://yggdrasil-network.github.io/

deleted by creator

theres also nebula and netbird

oh shizz
really? i was just kidding. aah ITS EVERYWHERE

if theft is a concern. record IMEI number and they(carriers etc) will probably blacklist the phone from mobile networks and maybe aid the tracking(investigation…if any). which, afterwards, lowers resale value

is that like google??

good point. i did not realize that

yet another google “proxy” : https://www.lukol.com/

nssy

not gemini(protocol) .
not lynx .

other ai services do too. u might not realize it.

vyper has plans fo $3/mo

feels censored to me. i wouldn’t be surprised if u had poor results for torrenting websites.

I cant find any information that discusses the security risk. But it would seem that this transfering all content to the owner of the phone number is a standard feature.
So, maybe its not discussed because it doesn’t frequently happen.
It doesnt seem like a trustworthy way to ensure users’ content remains secure.
Update:
https://old.reddit.com/r/signal/comments/8r7tbc/someone_impersonating_me_using_my_old_number_what/
https://support.signal.org/hc/en-us/articles/360007062012-Change-Number
https://support.signal.org/hc/en-us/articles/360007062452-What-do-I-do-if-my-phone-is-lost-or-stolen
https://support.signal.org/hc/en-us/articles/360007059752-Backup-and-Restore-Messages

If someone trys to register with an existing number then it wont work if its already being used.
Im not sure on this^
Better to enable a security pin if you are concerned.
The traditional phone system involvement is annoying.

”It’s important to maintain control of this phone number."

I strongly feel that this is false.

This is what flatpak brings to the table

Diaspora has private groups. But many downsides.
For example… discovering people, first involves sharing with them.

mastodon on a homeserver. no public posting.