Mikelius

Nah same results :( maybe Firefox nightly mobile problem?

Just gave it a try… Doesn’t appear to work for browser default search settings? I do a search and see results for about 2 seconds before it then shows their search page. I used https://www.qwant.com?q=%s for the query. Liked the search results I tested it with but not being able to use the search bar for quick searches is a deal breaker for me :(

What I did was just buy the tv I wanted for the hardware and block it from internet access by Mac address, then plugged it into the network with eth. I then put dns blocks on every request it made (I log things before blocking them, and did this on the scenario a kill switch gets messed up or something) and installed the media software from there. Smart tv made private.

If you’re very technical and understand Linux, security, etc in great lengths (such as how to setup your own iptables rules with looking for help or creating your own scripts), and really know what your doing, a rooted non-gapps lineageos (optionally microg) is a great choice, as long as you install things like AFWall+ and such to lock it down a ton. Heavy emphasis on “understanding” what you’re doing here, since if you don’t, a rooted device could be bad on security.

If you’re not at that comfort level or have the time for that kind of stuff, GrapheneOS (unfortunately on pixel) is the best option.

If you don’t want to give Google any of your money, and you don’t want to go into the super low level system control with root, the best option is probably still lineageos with microg (or without if you don’t need push notifications for anything).

96% but it’s not accurate. Verified on my DNS logs that the two it claimed weren’t blocked, actually resolved to 0.0.0.0 correctly, so I’m actually at 100%

If you have geolocation enabled or don’t block location requests, that could be another way. VPN can’t protect you from geolocation.

Probably already said here, but it’s going to just come down to your end goal to know what distro fits what you’re looking for.

I am personally a huge fan of Gentoo, another distro that’s all about “from the ground up” approach. It’s actually where I started with Linux and is how I became as proficient in it as I am today. In fact my internal server that does everything is running Gentoo as it’s OS… Has never had any problems in the last decade that would require a reinstall or anything crazy like that.

But even as much love as I have for Gentoo, I have Linux Mint installed on my laptop. Why? Because it’s just more convenient when I need my full focus on the 10 other personal projects I’m working on… Also amazing on the gaming front. Doesn’t have nearly as much bloat as some other Ubuntu-based distros on first install, has a huge community support, and is just great all around to have.

Ah, I misunderstood you mounting the system in as your main, not a backup. Gotcha!

Why not just self host? What happens when/if their service goes down without any warning? You lose everything?

Got my things all on a server with RAID for redundancy and backup weekly to an external (encrypted) device, monthly to another that doesn’t stay at home. Also means I don’t have to rely on the Internet to use all my services if the ISP goes down, the firewall explodes, etc. Self hosting is the way to go!

Edit: autocorrect being annoying

Again, no Ubuntu expert here, so do this at your own risk (someone jump in and say this is a bad idea if it is). Not irreversible as you can just revert what I’m telling you via live CD, but just wanted to leave the warning.

If uname -r shows the old kernel *-24, and grub update is choosing that instead of *-25, perhaps Ubuntu relies on the last change/created date or something weird. What you can check is if *-24 AND *-25 show up in /usr/src. If both are there, do (as root/sudo): mv /usr/src/*6.2.0-24* /root. Now run grub-update again. I think it should tell you which version it chose for the boot menu.

Next try: grep 6.2.0 /boot/grub/grub.cfg to verify you see the new version.

• If you see it, reboot and see if it starts with it. If you can’t boot, go through the liveCD and move that directories back to /usr/src, chroot to the drive (see https://www.turnkeylinux.org/docs/chroot-to-repair-system for how to do this properly), and after chrooting, run grub-update again.
• If you don’t see it or get nothing back from grep, move the directory back and re-run grub-update to avoid not being able to boot back in. This wasn’t the fix we were hoping for.

^ this is all assuming Ubuntu puts its kernels in /usr/src and uses that location as reference to what’s available/installed. If you see nothing there, then something else will need to be attempted

Edit 2: another thing to check is if the compiled kernels are in /boot. Basically follow the same instructions above but use /boot/*-24 instead. This might actually be what needs to be done now that I think about it, not necessarily /usr/src.

Have you tried a normal “grub-update” command to make sure it gets the right kernel to boot up for you? Not 100% familiar with Ubuntu, but perhaps that’s all you’d need to run to get it booting to the right version.

Thanks! Came back to actually add an edit or reply to mention that I found an issue on darkreader issues with a resolution for putting in a custom filter to unlock origin! Worked perfectly.

https://github.com/darkreader/darkreader/issues/11325

Question in the issues that did come up is… Why are they doing this? Only reason as some others mentioned sounds like it would be for tracking purposes which contradicts what their model is about. Seems like there’s no winning search engine for privacy, just the least of all evils? Lol. Glad to at least be back to using it for now.

Love it except I can’t use it because I don’t save cookies to keep the “dark setting” enabled and dark reader doesn’t automatically invert it, likely due to them breaking some sort of common html/css standards if I had to guess. Wish they would fix it for accessibility. :(

Dunno if anyone mentioned it, but if I had to guess, you have a DNS leak. Basically your DNS requests are going through your ISP instead of the VPN, resulting in them knowing where you’re going online anyway. Be sure to check for those DNS leaks and setup a custom one if your VPN doesn’t offer one. Don’t forget, DNS traffic over port 53 is also unencrypted, so unless you force those through the VPN, they could still know where you’re going.