Idk, I can’t tell the difference between the last 9 versions

Tell that to the “nontechnical” brick walls that hate you.

Not relevant. Unless you use airplane mode, it will be visible that your phone was at the place.

gaaaaaasp plz tw c*nsorship

That’s exactly the joke.

Grandfather is 5-bit opcodes on switches

You mean: a spoiler tag?

grandfather is python2

still mozilla

edit: I get it, stop replying

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.

On Ladybird, you can block yourself from supporting the devs

What are you actually broadcasting while doing so? That you are using KDE Connect?

That + device name which is probably pretty unique. Chinese routers scrape all of that. IIRC mDNS is actually disabled on Linux for now because it was conflicting with Avahi which broke some more stuff.

do not use KDE Connect on other networks

Last time I used it, I don’t recall a toggle for that in either the Linux or the Android clients.

Edit: what alternative device discovery solution could be used by KDE Connect to make it more private on untrusted ntetworks?

Exactly as it is right now but on a whitelist.

Offtopic but I am really annoyed by how many custom ROMs (especially LineageOS) disable MAC randomization at build time and make zero mention of it on the wiki/forum/whatever page. That’s just as important.

KDE Connect seems to send identifying broadcast packets constantly (just like gapps), not the best for privacy on public bing chilling router WiFi. Android itself technically does too, but you can just change your device name to " " (space).

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.

Gotta love promoting Electron slop like Element right next to stuff claiming sustainability

Despite sleep (the “wake up on every network event” kind of sleep) not being implemented in most PostMarketOS devices, I fucked around with my Redmi and found that the battery lasts much much longer on standby (if I don’t forget to close the apps because they won’t unload themselves)

If you have a whole ass Android container like Waydroid (instead of stuff like android-translation-layer being developed), you can just put MicroG there. Or whole ass Google services, if for some reason you decided it’s a good idea. It’s just Android.

But yeah, hardware support suckzzzz

All foam does, you need a unique property for the name

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).