I’m running e/OS in my old Poco F3 right now.

I switched from LineageOS because I though, e/OS would be easier to ungoogle.

In the end, it just defaults to way more compromises than I would have made on LineageOS.

Over all, it’s actually just LineageOS with MicroG preinstalled, a really bad launcher, an ugly 2015-ish iPhone icon theme, and a few mediocre apps preinstalled, that use these ‘Murena’ services that claim to be an alternative to Google services, but they are neither more secure/foss nor reliable.

Their appstore is rather Bad. Yes, it essentially combines something like APKMirror and F-Droid in one app, but it requests a Google account to access PlayStore Apps.

Imho, LineageOS with MicroG, no GApps, F-Droid and APKMirror and a few foss apps is the better solution.

I have my sync services selfhosted through a NAS and simply use WebDAV (backups), CardDAV and CalDAV. This was harder to set up in e/OS than in basic LineageOS, because e/OS is trying to push their own Murena services for that. And if I didn’t have all of these selfhosted, I’d rather use Proton services instead of Murena.

Over all, really sketchy. It’s like a custom Rom that claims privacy but actually just wants you to möge to their own service.

Well, they have a small point though:

By allowing to upload to a third party image host and allowing to embed images from other sites directly into Lemmy, the load on servers could be reduced while also allowing for larger/higher quality files.

This would obviously come with a downside to privacy.

The current solution would be: upload a highly compressed file to Lemmy and then link to the external high-quality version in the post.

An alternative solution from Lemmy devs could be, to allow external sources and hide the image until the user confirmed they want to load it from an external source. Or just… Add a toggle to settings to automatically load them.

I mean, with federation and all, everything in Lemmy is an ‘external’ source anyway unless you trust every single federated instance. So why not allow external image hosting/file hosting sites as trusted sources.

Up until a couple decades ago, basically all religious texts were distributed without getting consent, giving credit or forking over royalties to their original authors. Rhymes and songs, even images, were observed and then repeated or noted down and spread.

By todays definition, that’s piracy. Piracy is exactly the same thing, just in a digital world.

Therefore, if piracy isn’t halal, most religious texts and imagery aren’t halal either.

Now, looking at it the other way around, to confirm that:

Theft is illegal. So the question stands: is piracy theft?

That depends on the definition of theft. The old meaning of theft, so the thing, probably ruled over in religious texts, is: The unlawful taking of the property of another.

Now, can you take something from someone else, without them loosing it? I’d argue: No!

So, piracy isn’t theft. Piracy is copying or repeating.

I will revolt, once this tries to attack my privacy.

I’m fine, as long it complies technical requirements that applications will implement sooner or later, while preserving my privacy by simply defaulting to 1900-01-01 or something.

The systemd change ‘just’ adds a birthday field to the user data, where you could store (or don’t) the users birthday, that then could be used by other applications to request an age bracket.

The Arch-change doesn’t effect real arch Linux. It modifies the archinstall script (so, irrelevant, if you install according to Wiki) to ask the user for their birthday during installation and stores it for systemd.

Unknowingly?

Ingress was quite transparent about the goal of gathering real-world data to allows development of future technologies like self-driving and navigation.

It’s the reason, why I started playing it around 2012.

OK, yes, that obviously makes sense, considering the amount of these Charakters.

I know about it, but didn’t recognize the code. So I assumed, they encoded some text to make it harder to read. So I tried decoding it.

Turns out, if you decode this in UTF-16, it turns into a japanese sentence

契ȑ璝寣䇘앖噣삈

Which means (according to DeepL)

The sound of the wind rustling through the trees

And now I’m confused, why.