proprietary Google-only format

Keyhole Markup Language

KML became an international standard of the Open Geospatial Consortium in 2008.

(…)

The KML 2.2 specification was submitted to the Open Geospatial Consortium to assure its status as an open standard for all geobrowsers.

They probably fixed all the bugs they considered essential, and the rest is just nice to have fixes that can be moved to the next cycle if necessary (and they still have a week to work on them before release, although they might be careful not to introduce severe bugs now).

The general idea with this approach is that it doesn’t make sense to block a release on a few bugs worked on by only a subset of available developers and having the rest idle - the project can be finished faster by moving the remaining tasks over to the next release and accepting the bugs in the meantime.

Not familiar with the API, and I’m not entirely sure if it’s not just a bug in Eternity (fork of Infinity), but lemmy.one doesn’t have downvotes and I don’t get the option to downvote anywhere.

If you don’t sign into a Google account, you will never arm this mechanism at all.

The comment you replied to is a direct reply to the comment you linked - I don’t think it was intentional, but if it was, then I’d like to say it’s not a very helpful reply as OP already read it.

someone just plain lying about what OS they’re using in order to break fingerprinting.

The idea with avoiding fingerprinting is to look like whatever the biggest group of users looks like, because that’s who you share the fingerprint with. If you use an uncommon value for something, you make fingerprinting easier.

That’s one of the reasons why for example Vivaldi on Linux sets its user agent to match the latest version Chrome on Windows.

Seems more like a featureless slab to me

Fair enough. I misunderstood, my bad.

Then what’s the meaning of this whole part?

On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.

Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won’t help OP at all with their Arch-specific question, so it’s either that, or it provides contrast to the “corpo Linux”, which is how I interpreted it.

And here’s the remaining part of your comment I left out, just to make sure people won’t lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):

If you’re on arch you use redhat’s garbage.

On non-corpo linux syslog can be disabled

systemctl disable --now systemd-journald

I’d prefer to just symlink/mount /var/log to a memory filesystem instead

Set Storage=volatile in /etc/systemd/journald.conf

The huge amount of RAM on Android in general is less about supporting a single hungry app and more about keeping as many apps as possible in memory so that you can multitask between them without any of them losing their state. If one app manages to eat most of the memory, then it’s already too little for the intended experience.

Also the memory is supposed to be enough for at least the 7 years this phone will be supported for - that’s plenty of time for apps memory footprint to grow.

Maybe I’m biased by always having used devices with RAM size in the lower end (which is always also coupled by a not-so-great CPU so when you do run out of memory and the system starts killing apps you want to multitask between, you’re going to notice it that much more), but I’ll always take more RAM in a device that might survive a decade with a couple of battery swaps.

By taking away the MicroSD slot to force users towards expensive cloud storage?