lumina-desktop.org
“Home :: Lumina Desktop Environment”
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 loads is a page only: no own backend calls, wallet code, contract calls, AI services or live connections.E12
The real tech may live elsewhere. This page links to: github.com/lumina-desktop/lumina-website · check the code
What it is
- The Internet Archive first saved this site on 2015-07-26 (4128 days ago).E13
- The site describes itself as: “Lumina desktop environment project page”E2
- It's built with React (common tools for building web apps).E9
- In your browser it saves small bits of data in your browser.E10
- It has sections such as /features, /post, /index.html, /releases, /community and /faq.E11
Where your data goes
How key features work
Cookies and storage
Names only. We never store the values.
localStorageE7: https://lumina-desktop.org/variant
sessionStorageE8: https://lumina-desktop.org/visited-url//index.html
Pages and API calls
Pages it links to
//features/post/index.html/releases/community/faq/screenshots/index.xmlEvidence
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 8 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 XSgsneUr.