https://archive.today/I5h2o
Readit Newszeech commented on Fakes, Nazis, and Fake Nazis airmail.news/issues/2025-... · Posted by u/prismatic
zeech commented on Websites are tracking you via browser fingerprinting engineering.tamu.edu/news... · Posted by u/gnabgib
Has anyone made a plugin that forces your browser to resize slightly to help avoid fingerprinting? I feel like this is an annoyance I could tolerate, even if over the course of a day or two it causes me to resize it manually to something larger.
The name for that is letterboxing. The Tor Browser (and the Mullvad browser, based on the Tor one, and Firefox as of v. 67 with an about:config flag) all support it.
There are also add-ons that perform the same basic function with some added customisability [0].
[0] https://addons.mozilla.org/en-US/firefox/addon/canvasblocker...
zeech commented on AOSP project is coming to an end old.reddit.com/r/Stallman... · Posted by u/kaladin-jasnah
sad, was thinking to switch from iPhone to pixel 10 in few months once released exactly for the reason that is clean android and gives and escape hatch to use grapheneOS or lineageOS or calysOS. Any other android phone manufacturer that is supported by any of those projects? Most devices supported except pixel devices are few years old.
GrapheneOS only supports Pixels due to their having superior security features [0]. Calyx supports Pixels as well as some newer Motos and the Fairphone 4 and 5 [1]. Lineage supports tons of devices [2].
LineageOS is the only one of the three that supports older hardware, but I'd recommend getting a previous-gen Pixel for the seven-year (at least) support cycle.
[0] https://grapheneos.org/faq#supported-devices
zeech commented on AOSP project is coming to an end old.reddit.com/r/Stallman... · Posted by u/kaladin-jasnah
From https://calyxos.org/news/2025/06/11/android-16-plans/ -
> Google did not publish any device-specific source code for supported, modern Pixel devices.
> In previous years, Google released full device trees alongside new Android versions. This allowed developers to build and boot AOSP on Pixel hardware relatively easily.
> With Android 16, only the platform/framework code has been released. The device trees are missing, at least for now.
> This means AOSP 16 cannot currently be built or run on any recent Pixel device easily just using official source. It’s unclear whether this is a delay or a policy change. Either way, it seriously disrupts custom ROM development and our porting efforts.