Using English is the only way that all my colleagues are able to read it, but if it’s just meant for you, or only for Spanish speaking people, I’d say why not.
Using English is the only way that all my colleagues are able to read it, but if it’s just meant for you, or only for Spanish speaking people, I’d say why not.
I don’t understand the relevance of what you’re saying. Do you mean that the platform should have the right to allow biological females only (following the definitions of your law system)? Do you think that that’s implied when a platform is female only and defensible in court? Not a snarky remark, just genuinely curious what you mean. This case was all about gender identity discrimination and I don’t see how biological sex fits into the picture.
She had sued the platform and its founder Sally Grover in 2022 for unlawful gender identity discrimination in its services, and claimed Ms Grover revoked her account after seeing her photo and “considered her to be male”.
Judge Robert Bromwich said in his ruling that while Ms Tickle was not directly discriminated against, her claim of indirect discrimination was successful as using the Giggle App required her “to have the appearance of a cisgender woman”.
Judge Bromwich said the evidence did not establish Ms Tickle was excluded from Giggle directly “by reason of her gender identity although it remains possible that this was the real but unproven reason”.
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.
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.
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.
Average none, though 2.5 Gbps is getting more and more common and WiFi is catching up too. You could max out multiple slower devices at the same time without hitting the limit of your uplink. I don’t have a use case for that, so I’d only upgrade from my current 1 Gbps to higher speeds if the price is comparable. That doesn’t mean that others don’t have a use case for it.
Agreed. In the past you would pay for calling and text messages and data was often unlimited at the higher tiers, but since nobody pays extra for calling and texting anymore, they’re now charging for data. Luckily they can’t charge extra for EU roaming anymore.
Data caps on landlines is something that I haven’t seen for a very long time in my EU country. The last time I had a subscription with a data cap must have been with a 56k modem, if at all. Cable and DSL might have had fair use policies back in the day (or maybe they still do, who knows), but no hard cap. Or at least not that I can remember.
Internet nowadays is way too important to have data caps, especially at home. 5G should definitely be next. Differentiate in speed all you want, but ditch the caps.
I’ve checked and you can find it on the settings page in the general section. I’ve briefly tested it and it seems to do what it says, but of course it fully depends on comments and posts being correctly labeled. I suspect that many people don’t correctly label their posts and comments. I know I don’t.
Doesn’t Kbin filter based on your language preferences? And even then, English is used by non-native speakers (such as myself) as well, because it’s the language that most people understand and it allows you to speak to a much larger user base.
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.
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.
I think that the idea is that by setting a strict deadline after which women can’t have children or marry, they are forced to start a family now or risk regretting it later. That’s the only way I can make sense of this bizarre scenario.