I might be wrong, but I think they will probably let the OS handle the biometrics offline, which means that they won’t have access to your biometrics, they just work with cryptographic keys. Otherwise it doesn’t make sense, as apps usually don’t have direct access to the fingerprint reader. It will probably be similar to how a passkey works.
The black one is the 1x and is the tastiest of the three in my opinion. The 3x seems to be tastier than the 2x (both red), but that’s based on memory, as I haven’t tasted them side by side. We buy the 1x quite often and add some extra ingredients to it (egg, spring onions, crispy chili oil, cheese). It’s spicy, but not extremely so according to our taste, especially not with the extra ingredients.
What you might be referring to is the question whether you’d like to import the GPG key for that repository. That happens when you first install a package from that repository. Could that be the one? I’m not aware of any other prompts.
For me it works fine, but I guess that might be because I use the flatpak version of Firefox.
deleted by creator
A non-political event, eh? Interesting: https://www.theguardian.com/tv-and-radio/2022/dec/30/eurovision-chief-russia-ban-stands-for-ultimate-values-democracy.
But then when you’re talking about 10:00 hours without specifying anything else, it actually means something completely different in the local context, apart from it being the exact same time globally. It doesn’t tell you whether it’s night or day at the other persons location. Your default point of reference in that system is the world, while even today, time is mostly used in a local context for most people. When I’m talking to someone abroad and I say “my cat woke me up at 5:00 in the morning”, I expect the other person to get the meaning of that, because the other person understands my local context.
When planning meetings you’d have to now the offset either way, because I’m not going to meet at idiotic times if there is an overlap in working hours between the two countries, which is something that you’d have to look up regardless of the time system. And if I send out a digital invite to someone abroad, the time zone information is already encoded inside it, and it shows up correctly in the other person’s agenda without the need to use a global time. In that sense UTC already is the global time and the local context is already an offset to that in the current system. We just don’t use UTC in our daily language.
But if it helps: I do agree that in an alternative universe the time system could’ve worked like that and it would have functioned. I just don’t see it as a better alternative. It’s the same complexity repackaged and with its own unique downsides.
But with such a system in place, what are we actually solving? If we’re agreeing on offsets (which would happen in a sane world), we’re just moving the information from one place to another. In both systems there is a concept of time zones, but it’s just the notation that’s different, which adds a whole new bunch of stuff to adapt to that’s goes very much against what is ingrained into society, without offering much in return. It’s basically saying “it’s 10:00 UTC, but I’m living in EST, so the local offset is -5 hours (most people are still asleep here)” [1]. Apart from the fact that you can already use that right now (add ISO 8601 notation to the mix while you’re at it), it doesn’t really change the complexity of having time zones, you just convey it differently.
Literally the only benefit that I can come up with is that you can leave out the offset indicator (time zone) and still guarantee to be there at the agreed time. Right now you’d have to deduct the time zone from the context, which is not always possible. That doesn’t outweigh the host of new issues that we’d have to adapt to or work around in my opinion.
[1] In practice we would probably call that 10:00 EST, which would be 10:00 UTC, but indicate the local offset.
Sure, but roughly speaking you know that 14:00 local time is probably okay for a business call, whereas 2:00 local time is probably not. You can get that information in a standardized way and the minor deviations due to local preferences and culture can be looked up or learned if needed. In contrast, with the other system there is no standard way of getting that information, except for using a search engine, Wikipedia, etc. The information not encoded anymore in the time zone, because there is no timezone.
Also, consider this: every software program would have to interpret per country what “tomorrow” means. I mean, when I’m postponing something with a button until tomorrow morning, I sure want to sleep in between. I don’t want tomorrow morning to be whenever it’s 8:00 hours in my country, which can be right after dinner. That means yet again that we need to have a separate source giving us the context of what the local time means, which is already encoded in the current system with time zones.
Not to mention the fact that it’s plain weird to go to a new calendar day in the middle of the day. “Let’s meet the 2nd of January!” That date could span an afternoon, the night and the morning after. That feels just plain weird and is not compatible with how we’re used to treat time. Which country will get the luxury of having midnight when it’s actually night?
Until you’re talking with someone from another country and you have no shared concept of time. Or you’re going abroad and you have to relearn what the numbers mean to fit the schedule. In the current system the numbers mean roughly the same in any country you visit.
Because time relates to the position sun and tells us something about what period of the day it is in that timezone. Your proposal would strip off that information, which means that you would have to look up in a different system what the business hours are in another country, when it’s night, etc. That means that you’re basically reinventing timezones by putting them in a separate system, which defeats the purposes and makes it more complicated than it already is.
Sure, time differences might be a bit cumbersome, but timezones have a name and can be converted from one to another. Also, most digital calendars (for meetings, etc) have timezone support and work perfectly fine when involving people from multiple timezones. To find a good moment to meet, you will still have to keep the time difference in mind, but in the current system you can at least take it into account just by looking at the time difference.
Maybe to make the article seem shorter, so you’re more inclined to keep reading. Once you’re halfway through, you’re more likely to want to read the rest. Both halves are probably filled with ads, so the longer you stick around, the better.
What you describe is default for me. I can type “test 123” in the URL bar, which looks up that phrase with my default search engine, and if I select it again, I can edit or copy the original search query “test 123”. It doesn’t show a URL. You can configure that setting on the settings page where you can configure your default search engine.
In my opinion as an outsider (and one that uses a normal keyboard and doubles up on keys just like you do) many comments here are genuinely trying to be helpful. You’re asking for a layout that fits your current typing habits and based on their knowledge and experience they’re telling you that you might want to drop that habit instead. That’s advice and you’re not obligated to take it. It seems to me that you’re misinterpreting a lot of those comments as criticism.
Well, all communities that people on your instance have subscribed to. But the comment your replied to didn’t say it wasn’t, right? They use it to discover new communities to subscribe to.
The regulation actually enforces that PD is implemented if high speed charging is available and that it can’t be limited in speed compared to any other charging protocol that’s also available on the device, irrespective of the charging device used.
We don’t need to guess if we can just read the regulation: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32022L2380&qid=1691523718368.
I’m using Kagi, which aggregates search results from several search engines (including their own), but without the ads, with less crap and with features like searching for literal strings and promoting/demoting certain websites. It’s a paid service, though, but I like it enough that I’m ok with that.
In the Netherlands it’s now mandatory to use the lowest price of the previous 30 days as the base price. I believe that it’s based on EU legislation that will follow. I noticed yesterday that amazon.nl still ignores this and uses the “suggested retail price” instead (even if they’ve never used it).
Given the constraint that the notch can’t physically be fully covered with pixels, I actually consider the pixels on either side of the notch to be extra pixels. However, the OS should play media in a rectangular shape, i.e. not using the extra pixels on either side of the notch. Of course it would be even better if there was no notch at all, but not at the expense of having less pixels overall, in my opinion. Those pixels can be used for status icons and such. I agree with your other points.
In my opinion it’s more useful to look at grams of protein per kcal. You can only eat so many calories in a day, so that dictates your protein intake for a large part. If you eat 2000 kcal worth of peanuts, you’d ingest 80 grams of protein. With chickpeas that would be 110 grams and with chicken breast 425 grams. You don’t eat just protein rich things, so the higher the value, the higher your chances of ingesting enough protein when combined with (other) vegetables, grains, rice, oil, etc.
I know that some people will read this comment as if I’m promoting meat consumption, so let me add that I firmly believe that the world would be a better place if we ate a lot less meat. I’m just using these examples for demonstration purposes, as they’re all at the right side of the graph. It’s always an option to supplement with a plant based protein powder.