The most interesting finding from using EVs in winter is not that they consume more energy (which they do), but that charging is really slow if you don't have battery preheating. Yesterday, I arrived at a 240 kW charger with 33% SoC, the outside temperature was 0°C, and the charging power was only 35 kW (the maximum charging power of the car is 118 kW). With this charging power, it would take 40 minutes to charge to 80% SoC. We don't mind too much because we primarily use the car as a city car and do 95% of our charging at home, but if you want to have an EV as your only car and drive long distances with it even in winter, definitely get one that has battery preheating.

#EV #electricVehicles #emobility #electricCars

in reply to Thomas

@tpheine yes, it is still limiting, my brother-in-law drives to customers spread across the whole country and time is of essence. He says he still cannot afford an EV because of this, so he has a diesel Škoda Superb. I think this will be pretty much solved with the 800V architecture which is slowly getting into this segment. A good example of this is the new BMW iX3. Its drive range is over 500km even in winter, the maximum charging rate is 400 kW and can charge for 350km in 10 minutes. Once EVs with such parameters are more widespread, most of the opposition will disappear. It's already a completely different world than my 3-year-old Audi with 35kW charging in winter. 🙂

Ten paciencia cuando se confunde.
No la apresures cuando tarda en recordar.
No le quites valor a sus palabras cuando repite una historia que ya conoces.
Porque antes que nada…
sigue siendo tu madre.
La misma que respondió tus preguntas una y otra vez sin cansancio.
La que secó tus lágrimas, incluso cuando no había motivo.
La que veló tu sueño cuando el cuerpo te ardía de fiebre
y el mundo parecía demasiado grande para ti.
Hoy sus pasos son más lentos,
su memoria a veces se dispersa
y su cuerpo se fatiga con facilidad.
Pero su amor no ha cambiado.
Ese amor sigue firme, atento, completo… como siempre lo fue.
Hazla sentir importante.
Hazle saber que su presencia cuenta,
que su risa sigue teniendo lugar
y que su vida no es una carga, sino un regalo.
Abrázala sin prisa.
Escúchala aunque repita.
Quédate un poco más.
Porque llegará un día en que ese lugar quedará vacío,
y darías cualquier cosa
por escucharla contar su historia
una vez más.
Ama hoy.
Cuida hoy.
Porque el amor que se posterga mañana pesa más de lo que imaginas. 🤍

The greatest piece of advice I was ever given was this: when you stop work for the day, never stop at a 'clean' break point; stop in the middle of something you can finish easily.

That way the next morning you're not confronted with a a dauntingly blank page or an empty function to write, but a half-finished one you can get back into without difficulty.

I can't remember who gave me that advice, but I've stuck to it dogmatically whenever I can.

This entry was edited (1 day ago)

I was recently reminded of this.

A couple decades ago, I wrote a short paper that described how the basic approaches of cryptography and computer security lead to an efficient and practical privilege escalation attack against master-keyed mechanical locks, which I published in IEEE Security and Privacy (a nerdy computing technical journal).

mattblaze.org/papers/mk.pdf

TL;dr: Master-keyed locks have fundamental, exploitable weaknesses.

But I wasn't ready for what happened next.

1/

This entry was edited (2 days ago)
in reply to Matt Blaze

It occurs to me that people outside the security field might find it odd that we openly publish stuff like this. Why help people who might use the knowledge to do bad things?

There are a number of reasons. The first is that only through open discussion are we able to identify and fix problems. Another, which is what motivated my work, is educational: you can't learn to defend systems unless you understand how they are attacked.

MORE USPS FUCKERY

The USPS just changed the meaning of a postmark. Under the old rules, when you dropped the mail off at the post office was the postmark date.

Now, the postmark is the date your mail was first processed by an automated center.

If you drop your mail off Monday but it doesn't get processed until Wednesday, Wednesday is the new postmark date.

Yes, this can affect taxes, healthcare, and-- not coincidentally, I'm sure-- ELECTIONS.

nstp.org/article/usps-announce…

#USPS #Trump

in reply to Scary Austin VOTED 4 HARRIS!

but this is how it always was. If you drop your mail off into their possession (big blue drop box) but they don't pick it up until tomorrow and process it at the local post office, the postmark is tomorrow not today ...

Yes they will absolutely use this as a way to sceew with mail in ballots by disrupting processing of those too close to the deadline (understaff, shutdown USPS, etc) and now there will be little chance of successfully challenging it. At this point Trump could legally fire EVERYONE at USPS weeks before the election to screw everyone over too and he probably will.

The conversation about AI is exhausting, and I'm finding myself more and more talking with my friends about its dangers and downfalls.
I definitely see a new level of awareness and skepticism coming from non-tech people, which is great.

One question that sometimes come up with people wanting to learn how to code is "Is it worth even doing it with all this AI self coding tools?"

Hell yeah! Absolutely! Technical literacy is even more important now than ever!

youtu.be/g5IRn0OzzU4?si=EjUgEw…

U.S. distillers complain Canadian provinces favouring local alcohol

ctvnews.ca/toronto/politics/qu…

LOL. You elected your leader. Complain to him.

Editional tips and tricks for downloading the cops pack

Sensitive content

This entry was edited (1 day ago)
in reply to Bri🥰

Editional tips and tricks for downloading the cops pack

Sensitive content

Is there a tool that will either

- let me run a script over files in a directory tree in parallel
- re-encode a directory tree of music files in parallel

while being robust about interruptions (don't have to restart if I interrupt it and run it again), etc.

I'd rather not write this even though it would be a good little exercise.

(I need to recompress my music collection, for my car's stereo, and it needs Very Particular metadata.)

in reply to Federico Mena Quintero

I know you have a solution already, but what file format are you targeting? e.g. if your source and target formats are FLAC then metadata-only updates in parallel should be clustered by album because metaflac(1) can take some shortcuts; if it's MP3 specifically then you'll want to group files into batches because id3v2(1) starts slowly; if you actually need to re-encode and not just update metadata then you might need to disclose your core count; etc etc
in reply to Ben Zanin

@gnomon I'll need mp3 and was thinking of batching all tracks in an album, which kinda matches my laptop's number of cores.

I need to experiment a bit with the stereo first; it doesn't pick up the track number field, so if it just sorts an album's tracks in alphabetical order I'll need to tell ffmpeg or whatever to output track numbers as part of the track name.

(everything is in flac; I need mp3 smaller than the bitrate I used initially, or music won't fit in an USB stick)

in reply to Zach Bennoui

That's really cool, congrats! Just one thing, please please please don't use the Claude-generated code to learn SwiftUI… SwiftUI has gone through several very significant changes since its introduction, so there's a lot of still working but deprecated API in there, and Claude absolutely loves to use the outdated methods. So, if your goal is just to have some great fun with it and quickly build some fun projects for yourself and maybe some friends, this is absolutely, totally fine. But if you actually want to get into Swift and SwiftUI for real, I'd be more than happy to send you a link to an absolutely amazing tutorial series, which will teach you all you need to know from beginner to expert.

We are receiving reports that Google flags our repo as "having dangerous apps" or being a "dangerous site" – texts being very vague, no proof given (nor did they inform us). They also link to a page they call "Transparency Report" – which is of the same vagueness, but definitely not transparent (transparencyreport.google.com/…)

We're not aware of any such dangerous content. All apps on our repo are properly scanned, see izzyondroid.org/about/security…

#IzzyOnDroid #serviceToot

in reply to IzzyOnDroid ✅

I guess that any site with open source and transparent content is for Google suspicous . Other sites use other safety measures not supportet or not under control by Google. For a big tech giant like Google other sites trigger more often alarms without really be carefull about the "foreign" content. Means also Google may try to confuse or irritate or manipulate others who are not following Google ?