Natanael

@Natanael@infosec.pub · Joined ⁨Jan⁩ ⁨2025⁩

Cryptography nerd

Fediverse accounts;
@Natanael@slrpnk.net (main)
@Natanael@infosec.pub
@Natanael@lemmy.zip

Lemmy moderation account: @TrustedThirdParty@infosec.pub - !crypto@infosec.pub

@Natanael_L@mastodon.social

Bluesky: natanael.bsky.social

Replying to @⁨ryannathans@aussie.zone⁩

1 C is defined relative to 1 hour for full discharge and 3 C means a 3x faster discharge rate (full capacity can safely be discharged in 1/3 hour, or you can discharge 3 cells sequentially in an hour). Good lithium cells tend to be above 5C, can reach 10C for peak load or if cooled.

For a large enough battery it doesn’t really matter, but for dense portable ones a lower C rating means you have to discharge from more cells simultaneously to maintain a given output. That makes it more complicated, and you have less headroom to the battery’s maximum Watt output if you need to accelerate a car hard suddenly.

Replying to @⁨MentalEdge@sopuli.xyz⁩

The problem is Google is treating all those functions (“tool calling”) as just any other response, they didn’t even bother training the model to recognize and process the requests properly using the tools. They did the Google thing of just putting the function in and calling a day and forgetting about it.

So without proper reinforcement learning it responds with the same casual randomized answer-shaped sequence of words as ever, you’re just lucky if the part of it that knows to look up the tool call instructions responds, and luckier if it does it right AND submit the tool call formatted right. If it forgets to look up it’s tool call instructions, it might randomly tell you it can’t do it because you got an answer from a part of the network trained on data from when there weren’t models that could.