Actually, webpages that mention it get blocked from what I’ve heard. But there’s no way to know if a videogame chat will have it (especially if TLS/SSL is used), so it wouldn’t happen there.

I was also bored one day and made this image in response to someone sending the same thing but about Lidl

Ukrainian here, smaller town. Most stuff is purchased on a street market a.k.a. bazaar. But there are also two competing grocery chains, Tavria V and ATB. It’s like RED and BLU. Left twix / right twix situation. They are everywhere. Anything that isn’t no-name (and is food) is probably cheaper there than at a bazaar. Though I once saw them sell tiny ass stollen loafs for 12 whole bucks because “it’s a slightly niche foreign recipe so it must be expensive” (and same with pretty much everything else in there). Might not sound like a lot but this is a week worth of (other) food, idk how much stollen costs for neighboring countries but went on amazon.de and scrolled for a little bit to find a similar thing for 2 euro.

Bigger cities have one or two really large (3+ story) buildings, which are renting spaces for the two competiting grocery chains, arcade halls, casinos, pizza/burger stuff and small stores selling random foods by weight. When one enters, all sense of time is lost.

Unless I an seriously misunderstanding, a 5$ wrench would be used instead of that “torture nexus” and then someone has to pay for giving shitty equipment.

All problems eventually lead to slowly solving overpopulation

Oh, see, unlike on x86 where you have the ACPI to detect hardware with minimal device quirks (still a lot of them), everything else doesn’t have that. Well, except some Qualcomm chips, but their implementation sucks and basically only works reasonably with Windows and Windows Phone. So you need a device tree blob (DTB) to tell the kernel where everything is. But enabling all of the drivers in a single kernel build makes it not fit (the partition for that is traditionally quite tight), so you make different kernels per device.

AND, on Android in particular, lots of features need device specific configuration for all of the small stuff like the proximity sensor and the cameras (a LOT more complex than webcams). This + the need for OEMs to insert their own spyware and the already existing tradition at the time to make device specific images made the decision stick around. There’s GSI, which basically forces the OEM to write drivers and all of that with a stable-ish API to make universal images possible, but it results in a system with lots of tiny inexplicable problems that slowly make you loose your sanity in my experience.

How postmarketOS handles it is that there are basically meta packages per device that depend on the kernel package appropriate to the device (sometimes for a whole platform or SoC, having multiple DTBs inside for each device) that flashes itself to the appropriate partition via a post installation hook, as well as all of the config files for apps that need device specific stuff and don’t already have it upstream (like camera apps).

I use MUSL/Linux on a tablet btw