that’s a whole lot easier said then done, especially with gmail’s dominance and strict filtering, and of other even obscure providers. mailbox.org then or something like that

you mean, unseparated from the rest of the trash?

takeout

takeout

sounds good on paper, but it cannot be a perfect thing as camera positions cannot really be up to date on any map

that’s your real problem. why, though?

are you using a content blocker? ublock etc

they shouldn’t seek a global ban on it?

First, the original dev continues to collaborate still,

I don’t think that means much. didn’t the new maintainer say they were given access to the original maintainers account?

two things can be true I guess

yes. normal usage works as expected

with the option to opt out then fine.

you cannot opt out from being visible on camera. that answers the question to me.

not only that, but I remember Firefox (maybe chrome too) announcing a few years ago they have made scripted timers less accurate. I think that was a mitigation against websites attempting a spectre/meltdown attack. how is it that this new attack is not affected by the inaccurate timers?

I would care if they haven’t fucked people over and especially the open source community.

that’s probably the BIOS only loading the configuration on the first boot. you could try enabling fast boot or disabling the right energy saving settings in the BIOS and see if that fixes it.

The only limitation I know is WOL doesn’t work after a power outage, because the switch and RPI doesn’t know where to find the target machine

maybe, but the pi does not need to know that, only the mac address and the interface. the switch doesn’t need to know either because it’s a broadcast frame, it’s forwarded to all cables. the problem sometimes is that if you configure WOL from linux, the network adapter will probably forget on power cycling that it is supposed to react to magic packets. I think not all hardware is susceptible to that, but even then it could help to configure WOL in the BIOS

@SuspiciousCarrot78@aussie.zone

Nobody is misleading you because you have deeply held ideas on what words should mean.

if your definition of encrypted means telegram is an encrypted messenger, than “encrypted” is literally nothing more than a meaningless buzzword, since all messaging services do some kind of encryption.

another important aspect is webapps also cannot communicate with native apps without you noticing it, while native apps can communicate with each other freely, entirely in the background. if you somehow block internet access to an app that includes google tracking libraries or those of another data broker company, it can just send the data it collected to another app with the same libraries that can still access the internet.

Technically all apps are continered on android, but the permission system is too lax.

i would be skeptical with your comment instead, because I think it has no basis in reality. you did not really say anything concrete about why you think so.

its not even about the permissions, but the API capabilities, and restrictions on background operations. web APIs provide much less access to the operating system than the OS APIs allow, even when given all the permissions. a webapp can’t read all your pictures, can’t access your contacts or SMS messages, because there are no APIs that would allow that.

there are some more intrusive APIs in the web standards that are not really useful for other purposes than misusing them for user data collection, like the battery statistics API or the gyroscope API. but as you see, choosing a browser that respects your privacy will cover that, because while chrome implements it, firefox does not