realityrevolt.com
“Reality Revolt — See In The Dark | Dimitri R”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
What it is
- The Internet Archive first saved this site on 2018-08-20 (3012 days ago).E23
- The site describes itself as: “Independent documentary series by Dimitri R. 10 episodes exposing hidden mechanisms of control. See in the dark — wake up to the reality beh”E2
- It's built with Next.js and React (common tools for building web apps).E7E8
- Notable building blocks in its code: Supabase client.E9
- In your browser it saves small bits of data in your browser.E13
- It has sections such as /serie, /en and /_next/image.E18E19
Where your data goes
Analytics & trackingCount visits and record what you do on the page. 1
| www.googletagmanager.com | Google Analytics / Tag Manager: Google's visitor analytics and tag loader | 1×E5 |
AdvertisingShow ads and follow you across sites to target them. 1
| pagead2.googlesyndication.com | Google Ads / DoubleClick: Google's ad network (serving and measuring ads) | 1×E6 |
Crypto and wallets
How key features work
Connecting your wallet
It connects to crypto wallets using personal_sign and eth_requestAccounts. Connecting shows the site your wallet address; it doesn't move funds by itself.E21
personal_signeth_requestAccountsMeasuring what you do
Visits and clicks are measured with Google Analytics / Tag Manager, Google tag (gtag.js), Meta Pixel and Vercel Analytics (found in its traffic or its code).E5E10E11E12
Google Analytics / Tag ManagerGoogle tag (gtag.js)Meta PixelVercel AnalyticsHow ads get picked
Ads are chosen through ad networks and exchanges (Google Ads / DoubleClick); they receive details about your visit to bid on the ad space.E6
Google Ads / DoubleClickSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E13
local_storagePages and API calls
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 11 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id u3kRgm4C.