IceFoxX
With all original Qualcomm’s CVE's. The next honeypot.
Dafuq... Want a top super secret tipp? Snowden leaks... and wikileaks...
yawn It’s as if people are actually pretending that uXDT and other tracking methods are something new... TVs, cell phones, smart devices, IoT devices, etc.—of course, everything is affected... Back then, some tracking methods were mainly used to track offline devices far away from a network... The whole thing just kept evolving... The fact that people are now bringing this up in relation to Ali, even though it’s even more prevalent in Western products... Or advertising using ultrasonic sounds. (Hehe, or in stores...) And if you think about side-channel attacks now—for example, the characteristic sounds from hard drives, CPUs, etc.
And when you consider what came to light about these issues through Snowden and WikiLeaks.
Whether it’s the U.S. or Europe… both are steadily eroding democracy… But of course, you worry about what they’re tracking about you in China, not what your own countries are tracking about you—and how that could end really badly… Just think about it: if Hitler had had access to something like that—oh my…
Data protection and privacy are important to me. (Here comes the joke.) Since I haven't had a VPN for a while (I need to sign up for one again, but I'm such an idiot—I always put it off and only think about it when I'm short on cash. xD) and I haven't set up DynDNS either, I only use Yacy locally.
Back then, I was running it on a Raspberry Pi 3B (now a Raspberry Pi 5) and hosting it via P2P. But I also had a VPN and so on.
So far, I've been a bit too lazy to set up Yacy completely on the PI 5. I'll be honest—since the settings are really powerful, it can take quite a while to get everything set up. 😅🤣
So I only use it locally on my Raspberry Pi and access it from the network. Accordingly, the results only include what I crawl (these are recrawled after a specified time to keep them up to date in case content changes, is removed, or is added on the actual websites). You can configure how deeply it should crawl and whether it should include links to other websites, etc. I’ve just set a shallow crawl depth of, I think, 3 or so. But I also search regularly with DDG to find other websites that I then add to the index for crawling. (This would be unnecessary for P2P operation.) That’s how I keep expanding it. You also have to set limits on the crawling; otherwise, it’ll use up all the network bandwidth if the computing power allows it. I don’t really use any of the customization, filtering, or ranking features, but I still took a look at what could be configured there—and there’s really a lot, so you can completely tailor the search engine to your own needs. It’s a little unfortunate that it’s based on Java
Here is a list of public Yacy instances that anyone can use: https://yacy.space/ ( ofc this works just p2p because someone else is hosting)
Yacy p2p search engine.
Run global p2p, Intranet p2p or local only. Crawl the web yourself.
Customizations.
Filtering.
Ranking.
etc.
I'll just do without the contacts then. I'm not going to let work force me into it just yet, even though it's used all the time there. I don't give a damn if it puts me at a disadvantage. Well, more and more people are switching over these days.
I can say "hey signal or similar. Otherwise go fck yourself".
What I can't do anything about is that these people are also giving my data to Meta... Their phone book, etc., which is scanned and also contains my data.
People who have used it should take a closer look at data poisoning. In other words, they should generate a very, very large amount of false data. (Well, not just those people... but those people in particular should definitely do it. )
Nevertheless, there are also older, effective tracking methods (including GrapheneOS, etc.—well, anyway...) even for TVs predating smart TVs, etc. One such method would be uXDT. Lets dont forget side channel attacks
Thanks to LLMs, today's attack vectors have changed so drastically that it's already impossible to keep up. You could check this out " Radware 2026 Global Thread Analysis Report"
You can install and uninstall anything with root privileges. There may be issues with system components, but that doesn't include stuff from Meta, etc. By the way, GrapheneOS also suffers from critical CVEs—several, in fact—specifically on the devices where GrapheneOS can be installed... Qualcomm and its closed-source drivers, which the GrapheneOS team can't do anything about. (But strangely enough, grapheneOS only runs on Google phones or devices with Qualcomm chips... The honey tastes so sweet from this honeypot. )
5 downvotes... Well have fun.
Qualcomm CVEs – August 2026
CVE-2026-25289
CVE-2026-21366
CVE-2026-24079
CVE-2026-24080
CVE-2026-24084
CVE-2026-25288
CVE-2026-24076
CVE-2026-24078
CVE-2026-24077
CVE-2026-25292
Additional Qualcomm CVEs Affecting Snapdragon
CVE-2022-40514
CVE-2022-40512
CVE-2022-33232
CVE-2022-33279
CVE-2022-25729
CVE-2022-25728
CVE-2022-33216
CVE-2022-33233
CVE-2022-33248
CVE-2022-33225
CVE-2022-33246
And so much more..