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.

Pixel - varies by manufacturer

That was the Nexus line, Pixel phones are all made by Google. Although Pixel 5 series and older use Snapdragon SoCs, while 6 onwards use Google’s custom Tensor based on Samsung’s Exynos. The major downside is IMHO the awful modem efficiency - if I want to keep mobile network on so that I can receive calls, my 7a is limited to 2 days of battery life if I’m lucky (and that’s with barely using the phone, just a few pictures).

Edit: and I forgot to mention that all Pixels have great third party ROM support, except if you want GrapheneOS, in which case you need to go for the recent ones that are still supported by Google.

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.

deleted by creator

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

Nah, this development version is way worse than both Android 12+ design and Android 11 design - it just has random unlabeled tiles for system settings where you have to guess the meaning by the icon.

In Android 11, this was only used for the six quick settings you could access when you were looking at the notifications, and they would get labels when you expanded the settings side. In 12+, there are no unlabeled settings anywhere. But this redesign introduced unlabeled tiles for settings you don’t use often, which just seems insane to me.

Wow, first time I feel strongly about a quick settings update. It looks awful, taking the worst parts of the Android 12+ redesign and combining them with the worst ideas from the older design, like unlabeled icons.

It looks like there are unlabeled icons in the expanded state? Wtf? If I’m expanding the quick settings, that means I’m fishing for the less used settings, so there’s no way I’m going to remember that for example the weird circle with a small segment cut out means “Data saver”. It will just be a mystery icon that does some mystery action - that has nothing to do in a modern OS.

It looks like this design is heavily sacrificing usability for people who don’t spend hours every day mucking around with quick settings in order to please some hypothetical user who feels more slowed down by swiping over one or two screens than by having to find the one setting they currently need in a big matrix of poorly designed icons.

Edit: also it looks like the home screen is visible under the quick settings - I’m not a big fan of that, I really like the current design where the notifications are pretty much their own separate screen without distracting app content, but that’s just my subjective taste. Unlabeled icons are objectively bad.

How much Doritos dust are you willing to inhale?

Circle to search for music is pretty much just a shortcut to Google’s music detection available from the normal Google app

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.

You’re supposed to use fingers

That really depends on the technology used. For example, all modern Ethernet standards (which includes both copper and fiber optic) are full duplex, meaning they can provide the full bandwidth in both directions at once. So a gigabit Ethernet link can do a gigabit in one direction AND a gigabit in the other direction at the same time (but not two gigabits in one direction).

It’s easy to dismiss as an ad. I did, too.

Well, Vivaldi’s built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol

Where’s the article?

Salt from the seawater

In my very limited experience with my 5400rpm SMR WD disk, it’s perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.

40 MB/s sustained is weird (but maybe it’s just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn’t even slowly fill the cache)

Sounds like most of that would be handled by the kernel with non-Deck-specific modules - it won’t forget to notify the userspace that a device has disappeared just because it was in sleep mode at the time it was physically disconnected.

The only problems I ever had with sleep on Linux were all inability to wake up some part of the motherboard or the GPU because of crappy firmware, never with connecting/disconnecting external stuff.

Seems more like a featureless slab to me