oktoberpaard

@oktoberpaard@feddit.nl

• ⁨Comment⁩ on ⁨Is Telegram really an encrypted messaging app?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  They’ve implemented it in such a way that you only have access to an encrypted chat on a single device, so no syncing between devices. Syncing E2EE chats across devices is more difficult to pull off, but it’s definitely possible and other services do that by default.

• ⁨Comment⁩ on ⁨My opinion on Bone conduction earphones⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  For me they only work in relatively quiet environments, or with earplugs. As soon as a car drives by it completely drowns out the sound. With music that might not be an issue, but with podcasts or calls it’s very annoying. I’ve bought earplugs especially for this, as my other earbuds have issues with wind while running, but it does feel like it’s defeating the purpose a bit. I guess turning them all the way up would also work, but that doesn’t feel healthy. Other than that I like them and the mic quality is also good according to people I’ve spoken with over the phone.

• ⁨Comment⁩ on ⁨Why Charging Your Gadgets Over 80% Is Such a Bad Idea | iFixit News⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  I don’t doubt the fact that they take some margin to extend the lifetime of the battery, but if we take iPhones as an example, they:

  • charge at a slower rate when nearing 100%
  • try to postpone charging the final 20% until the last moment before disconnecting from the wall outlet
  • can be software capped at 80% by the user (in newer models)

  This makes me suspect that that the margin between what’s reported in software as 100% and the actual capacity of the battery is less than 20%. This also makes sense from the standpoint of the consumer expecting a long battery life on their expensive high-end device, putting pressure on the companies to make the margin smaller and the charging algorithms smarter. Just my observations, of course.

• ⁨Comment⁩ on ⁨Why has Firefox not removed third-party cookies, despite the fact that Chrome has begun phasing them out?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  I’m pretty sure that Chrome’s alternative is designed by Google to track you in a way that’s harder to block and gives them more control over the advertising market by forcing advertisers to play along and use their method instead of collecting your data directly. Sure, it’s more private, but it’s still tracking you.

  Firefox, on the other hand, is focusing on completely blocking cross-site tracking. They have no incentive to completely block 3rd party cookies as long as there is also a legitimate use case for them, but I guess they will eventually also block them if Chrome is successful in forcing websites to stop relying on them for core functionality.

• ⁨Comment⁩ on ⁨Why don't we have one timezone covering the whole earth?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  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.

• ⁨Comment⁩ on ⁨Why don't we have one timezone covering the whole earth?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  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 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.

• ⁨Comment⁩ on ⁨Why don't we have one timezone covering the whole earth?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  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?

• ⁨Comment⁩ on ⁨Why don't we have one timezone covering the whole earth?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  Until you’re talking with someone from another country and you have no shared conception 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.

• ⁨Comment⁩ on ⁨Why don't we have one timezone covering the whole earth?⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  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.

• ⁨Comment⁩ on ⁨Why do some websites have a "Continue Reading" button?⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  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.

• ⁨Comment⁩ on ⁨Heating and cooling Raspberry Pi 5⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Is there information available about the noise levels of the case? I only see noise levels mentioned for the active cooler.

• ⁨Comment⁩ on ⁨Is there a way to mass block lemmy communities?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Well, all communities that your instance is federated with. But the comment your replied to didn’t say it wasn’t, right? They use it to discover new communities to subscribe to.

• ⁨Comment⁩ on ⁨Over just a few months, ChatGPT went from correctly answering a simple math problem 98% of the time to just 2%, study finds. Researchers found wild fluctuations—called drift—in the technology’s abi...⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  That’s not necessarily true: arstechnica.com/…/googles-bard-ai-can-now-write-a…. If the question gets interpreted correctly and it manages to write working code to answer it, it could correctly answer questions that it has never seen before.