- Temperatures comping down.
- Did some refactoring on my project (allowing me to slowly decouple my code from a specific upstream library).
- Doggo back from holiday.
Aroop Roelofs
Tech | Rants | Cute anime girls
Pictures preserve moments.
Stories preserve memories.
Documentation preserves knowledge.
Remember this or you will be forgotten.
Discord: @finlaydag33k@social.linux.pizza
Matrix: @finlaydag33k@social.linux.pizza:finlaydag33k.nl
Keyoxide: https://keyoxide.org/c27fba8174a9c3ebfa5d512d738ee8dbc43f9861
>USA bans non-USA made routers citing "threats to national security"
>But random Chinesium IOT junk with 0 security is just fine still. ![]()
>Google Allows sideloading apps anyways.
>Requires 24h "cooldown period" to enable it.
>"If we can't fully stop it, we can at least make it extremely inconvenient"
For those wondering:
- The gear ratios are from the car's spec sheet.
- The torque values I got from putting it on a hub dyno.
Wheel sizes and final drive ratios don't matter as those are fixed anyways (unless we have invented technology to change wheels mid-drive already and I'm just behind).
Anyone who has experience with the M-DISC standard?
Is it any good?
Been looking at some non-cloud backup media in case my NAS fails.
Will primarily hold my photo archive and some other data.
:amiyarave:
https://www.youtube.com/watch?v=ZjZlheXCnqo
ポラリス ◇◆◇ キネマ106
World of "environmentalism", "sustainability" and "recycling"...
I may have to send a perfectly fine car to the scrapyard cus of a tiny piece of metal. : D
(Trunk won't lock, the replacement part is unobtainable and without it, the car will be rejected by APK and no longer street legal)
So, something from my car's buildlog made it into Google's AI summary (yes, it links my buildlog as the source and and only source for this)...
Problem for me isn't that Google uses it (that debate can go on for ages, not worth my time), the problem is that this "fix", isn't actually a fix.
It was a band-aid fix to make something work "alright-ish" for me to get certain usable data but isn't actually a proper fix.
It's incorrect information that has *dangerous* consequences.
Doing it this way gives the ABS module the wrong information (it'll think it's going significantly faster than it really is) which causes it to no longer function as it should (and trust me, unless you know what you're doing, you do not want to drive without properly functional ABS - and even if you do, you probably don't want to).
Google's AI is unaware of this because I never mentioned this in the buildlog.
To demonstrate, Image 2 shows my RPM from a log I've captured last year with my roadspeed but my car can not do 253km/h at just 3600RPM (5th gear doing 100km/h already does 3.2K and my car can't even go above 220km/h before being torque limited).
Just goes to show how blindly trusting Google's AI summary can have dangerous (potentially lethal) effects...
Yes, I am still working on a proper fix for this data but it's not expected anytime soon because it's not really a priority for me.
@daniel_bohrer@chaos.social Something for you?
New HoneyWorks Storylines? ![]()
- https://www.youtube.com/watch?v=Vd-RGW7FvSw
- https://www.youtube.com/watch?v=k7h-bGKWOeY